Gnus development mailing list
 help / color / mirror / Atom feed
From: Emanuel Berg <>
Subject: Re: how to kill a virtual group
Date: Sun, 30 Jan 2022 23:33:25 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Eric Abrahamsen wrote:

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

In general, stuff that are the same, it shouldn't matter where
or in what manner they are defined.

If they are not the same, then if something should or
shouldn't happen to them because of that, they should have
something so one can check - if they by accident look the
same, add some flag or something to the data
structure perhaps?

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

But isn't it better that stuff that aren't the same are
different to the point this can be determined just by
inspecting the very base data? To put that in the layers above
- indeed, how are those layers even supposed to find out?
Ask some third instance, where and how was this defined?
Just think one had to do that all the time, for example with
strings and integers?

underground experts united

  reply	other threads:[~2022-01-30 22:33 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 [this message]
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:

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