From: Eric Abrahamsen <firstname.lastname@example.org>
Subject: Re: how to kill a virtual group
Date: Fri, 04 Feb 2022 08:12:15 -0800 [thread overview]
Message-ID: <email@example.com> (raw)
Emanuel Berg <firstname.lastname@example.org> writes:
> Eric Abrahamsen wrote:
>> I think it would be weird if Gnus let you edit a server
>> you'd defined in your .gnus.el file, and then those edits
>> were simply overwritten next time you restarted Gnus.
> But then you get the situation now where the same stuff has to
> be treated differently ... which should never happen.
> Something like this could be used from .gnus.el and *Server*,
> alike since they, while different, should differ on the
> interface level only ...
> (defun gnus-edit-server (srv params &optional redefine)
> "Create or edit SRV with PARAMS.
> If REDEFINE is non-nil, overwrite existing data ..."
> ... )
> If people then choose to ignore that and instead edit the data
> directly in .gnus.el then yes, that would reset any in-between
> session changes, be it from Lisp or *Server* or any other
> thinkable way for that matter - and that's completely fine, it
> is that way with everything, and so it should. Set the integer
> to something, change it to something else, if it is set again
> on the next init that's what it'll be - I mean, what else
> would one have it be and how ever would that work?
> So interactive interface from Emacs (buttons etc), interface
> from Lisp (Elisp code); they uses the same setters and
> functions one level below to do the actual business; and when
> done, no worry and no record where the data was set.
Well, I understand where you're coming from, but I don't think writing
all this code and changing Gnus' behavior is worth it for some
conceptual idea of consistency and purity. With proper messaging to the
user (and non-buggy code) it's just not a huge tragedy.
prev parent reply other threads:[~2022-02-04 16:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 15:07 Uwe Brauer
2022-01-28 17:05 ` Eric Abrahamsen
2022-01-28 21:02 ` Uwe Brauer
2022-01-28 22:21 ` Eric Abrahamsen
2022-01-29 0:03 ` Emanuel Berg
2022-01-29 4:18 ` Eric Abrahamsen
2022-01-29 15:48 ` Emanuel Berg
2022-01-29 17:17 ` Eric Abrahamsen
2022-01-30 22:33 ` Emanuel Berg
2022-01-31 19:24 ` Eric Abrahamsen
2022-01-31 21:59 ` Emanuel Berg
2022-02-01 1:43 ` Eric Abrahamsen
2022-02-01 3:10 ` Emanuel Berg
2022-02-01 4:32 ` Eric Abrahamsen
2022-02-01 7:26 ` Emanuel Berg
2022-02-01 16:10 ` Eric Abrahamsen
2022-02-04 2:30 ` Emanuel Berg
2022-02-04 16:12 ` Eric Abrahamsen [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).