From: Eric Abrahamsen <email@example.com>
Subject: Re: how to kill a virtual group
Date: Sat, 29 Jan 2022 09:17:01 -0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Emanuel Berg <email@example.com> writes:
> Eric Abrahamsen wrote:
>> Right, I have read the docstring! And it is necessary to
>> keep servers defined in gnus.el separate from servers
>> defined in-Gnus, via the *Server* buffer.
> Okay, why?
Because the two kinds of server need to be treated separately. Gnus is
not allowed to overwrite your gnus.el file, so if you want to make a
change to a server defined there, Gnus can't do it via the *Server*
buffer: you have to shut Gnus down, edit gnus.el, and restart.
Conversely, servers defined via the *Server* buffer are saved in
.newsrc.eld, which only Gnus is supposed to touch, so edits should be
made via the *Server* buffer. Gnus needs to know which servers are which.
>> But my `gnus-server-alist' has only ever held the "archive"
>> server, nothing else, so that's obviously not right.
>> For some reason, servers created in the *Server* buffer
>> aren't added to `gnus-server-alist'.
> Same here, just the archive.
> I didn't know on could create servers in the *Server* buffer,
> even ... when and why do you do that?
Mostly by creating groups on the fly: nndoc groups to import old mail,
nnvirtual groups to combine other groups, nnselect groups for
searching... All of these will create their own server to hold them, and
if the group is persistent the server should be added to
`gnus-server-alist', and later saved in .newsrc.eld.
> Maybe remove the variable then, and create a new to just hold
> the archive stuff, if that isn't available in some
> gnus-archive-* already, and change references
> to that?
No, I think the main problem is that servers created in-Gnus are not
added to `gnus-server-alist'. Gnus has multiple layers of code for
finding servers, so often it works out okay, but in this case it isn't.
next prev parent reply other threads:[~2022-01-29 17:17 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 [this message]
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
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).