Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Make Gnus emit more errors for unknown servers?
Date: Sat, 29 Dec 2001 11:53:15 +0100	[thread overview]
Message-ID: <vafelleti04.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3d70ysmvp.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 29 Dec 2001 04:53:14 +0100")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> I think if Gnus finds a group name where no server exists, it just
>> creates a server on the fly.  So for example, if people add
>>
>>     (nnml "" (nnml-directory "/tmp/foo"))
>>
>> to gnus-secondary-select-methods, then create some groups in that
>> server, then accidentally delete that entry from
>> gnus-secondary-select-methods, Gnus will create a (nnml "") server on
>> the fly, and then it won't be able to open the groups.
>
> The server should still be in gnus-server-alist, I think?  If it
> isn't, it should be put there.  Probably.

I'm trying to suggest the opposite: when Gnus finds that a server is
missing, it should issue an error message.

There have been discussions in the past of people who see lots of
strange servers when they do `^'.  And even more strange problems
resulted from this.

kai
-- 
Simplification good!  Oversimplification bad!  (Larry Wall)



  reply	other threads:[~2001-12-29 10:53 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 [this message]
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
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=vafelleti04.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).