Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Make Gnus emit more errors for unknown servers?
Date: Mon, 31 Dec 2001 06:26:23 -0500	[thread overview]
Message-ID: <m3k7v3ocju.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <m3k7v5myxv.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 29 Dec 2001 23:41:32 +0100")

Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
> Let's say you have the (nnml "" (...)) server in your secondary select
> methods.  Your groups will put the "nnml:" server in the select method
> slot, and everything works fine.  Then the user removes that server
> from the secondary select methods, and Gnus then knows nothing about
> how to select that group.
>
> Wouldn't it be nice if that couldn't happen?  If Gnus were to store
> the server in `gnus-server-alist' (or some other variable), then the
> user could remove anything from the list of secondary servers, and
> nothing would break.

You're talking about defending against modifying
gnus-secondary-select-methods within a Gnus session, right?  I think
Kai is talking about editing the setting between sessions.  The next
time you start Gnus, and Gnus finds a group whose server is missing,
it should not be automatically created, because Gnus doesn't have
enough information to do it correctly.

Or do you mean that secondary servers should be stored in .newsrc.eld
just in case they go missing?  In that case, when would a server ever
be removed from there?


paul



  reply	other threads:[~2001-12-31 11:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-16 10:25 Kai Großjohann
2001-12-29  3:53 ` Lars Magne Ingebrigtsen
2001-12-29 10:53   ` Kai Großjohann
2001-12-29 10:55     ` Lars Magne Ingebrigtsen
2001-12-29 21:50       ` Kai Großjohann
2001-12-29 22:41         ` Lars Magne Ingebrigtsen
2001-12-31 11:26           ` Paul Jarc [this message]
2001-12-31 11:30             ` Lars Magne Ingebrigtsen
2001-12-31 11:36               ` Paul Jarc
2001-12-31 11:43                 ` Lars Magne Ingebrigtsen

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=m3k7v3ocju.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).