Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: how to kill a virtual group
Date: Fri, 28 Jan 2022 20:18:26 -0800	[thread overview]
Message-ID: <87fsp7kwdp.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87ee4rflwa.fsf@zoho.eu>

Emanuel Berg <moasenwood@zoho.eu> writes:

> Eric Abrahamsen wrote:
>
>>> Precisely this is the error I see! [1]
>>
>> Okay, this is something I've looked at several times over
>> the past couple years. I am not sure how to fix it mostly
>> because I don't understand the original intended behavior of
>> variables like `gnus-server-alist' and
>> `gnus-inserted-opened-servers'.
>
> `gnus-server-alist' has the docstring
>
>   Servers created by Gnus, or via the server buffer.
>   Servers defined in the user's config files do not appear
>   here. This variable is persisted in the user’s
>   .newsrc.eld file.
>
> I don't like the "servers defined in the user's config files
> do not appear here" part, exceptions like that are a bad sign,
> but as for what the variable expresses, it's clear what data
> it holds.
>
> `gnus-inserted-opened-servers' OTOH isn't documented. It is
> defined in gnus-srvr.el where it is then used four times.
>
> gnus-server-alist is used a lot tho, in several files. I think
> the "original intended behavior" is simply that it is used
> whenever it is needed :)

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.

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'.



  reply	other threads:[~2022-01-29  4:18 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 [this message]
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

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fsp7kwdp.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).