Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: *Server* buffer problems when adding server parameters
Date: Sun, 26 Aug 2001 18:28:27 +0200	[thread overview]
Message-ID: <vafu1yuss44.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m34rqx9iom.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 25 Aug 2001 00:50:17 +0200")

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

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> I think it should be "nnfolder:archive", not just "archive"?
>
> Just "archive".  It's the name of the server; not a group spec thing. 

This is all terribly confusing.  I think something should be done
about this confusion.  Probably, it's best to make things more
consistent.

Some time ago, there was a discussion about putting a server name in
gnus-secondary-select-methods, rather than the select method.  The
idea was that it is then possible to change the server definition
(parameters) without having to change all the groups.  Of course,
these days, it's not necessary anymore since .newsrc.eld stores
"backend:name" style thingies together with a group, rather than just
the whole select method.

But still, if some pieces of Gnus require me to say "mail" to name a
server, and others require me to say "nnml:mail", then I can be pretty
sure that the former pieces will get pretty confused if I have both
"nnml:mail" and "nnimap:mail".

Personally, I've got "nnml:" and "nnimap:".  Does that mean if I want
one of them to be secondary, I should do (add-to-list
'gnus-secondary-select-methods "")?  And if I do so, which one is then
secondary?  Both?

IMVHO, Gnus should use just two ways to specify servers and/or select
methods: the form thingy like (nnml "foo") and the string thingy
"nnml:foo".  What do you think?

kai
-- 
Symbol's function definition is void: signature


      parent reply	other threads:[~2001-08-26 16:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22 19:55 Benjamin Rutt
2001-08-23 16:50 ` Lars Magne Ingebrigtsen
2001-08-24  4:03   ` Benjamin Rutt
2001-08-24  9:43     ` Kai Großjohann
2001-08-24 16:09       ` Benjamin Rutt
2001-08-24 13:56     ` Lars Magne Ingebrigtsen
2001-08-24 16:07       ` Benjamin Rutt
2001-08-24 16:41         ` Lars Magne Ingebrigtsen
2001-08-24 16:52           ` Benjamin Rutt
2001-08-24 18:36             ` Benjamin Rutt
2001-08-24 22:32               ` Kai Großjohann
2001-08-24 22:51                 ` Lars Magne Ingebrigtsen
2001-08-24 22:27           ` Kai Großjohann
2001-08-24 22:50             ` Lars Magne Ingebrigtsen
2001-08-24 22:53               ` Paul Jarc
2001-08-24 23:00                 ` Lars Magne Ingebrigtsen
2001-08-24 23:12                   ` Paul Jarc
2001-08-24 23:20                     ` Lars Magne Ingebrigtsen
2001-08-24 23:31                       ` Paul Jarc
2001-08-24 23:46                         ` Lars Magne Ingebrigtsen
2001-08-24 23:53                           ` Paul Jarc
2001-08-25  0:11                             ` Lars Magne Ingebrigtsen
2001-08-25  5:21                               ` Paul Jarc
2001-08-26 16:28               ` Kai Großjohann [this message]

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=vafu1yuss44.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).