Re: Make Gnus emit more errors for unknown servers?

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Do you see the point I'm trying to make?  The user tries to change
> something about a server, but something happens so that Gnus does not
> use the new server definition for some groups.  Then my opinion is
> that Gnus should warn the user that something is wrong.  But the
> current behavior for Gnus is that Gnus silently adds the `missing'
> server.

Yes -- but my point is that a server shouldn't go missing.  :-)

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.

Of course, the list of servers would have to be synced with the
secondary server list, etc.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen