Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: funny problems with nnmail-cache and split-fancy-with-parent
Date: Mon, 20 May 2002 15:16:08 -0400	[thread overview]
Message-ID: <m31yc6wrxt.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vaf8z6ebq3h.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Mon, 20 May 2002 21:01:54 +0200")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> Maybe it would be useful for Gnus to define a certain standard as to
> what server names should look like.  I'm a bit confused.  Sometimes,
> it's nnml:foo, sometimes it's just foo.  People tried to explain to
> me before, but I still don't understand.  Must be a thickhead ;-)

A server has an "address", which is the "foo" part of "nnml:foo" or of
"nnml+foo:group.name".  A server may also have a "name", which is
"native" or the server's key in gnus-server-alist.  (Secondary servers
do not have "names".)  This is how the manual uses the terms "name"
and "address" - most of the time.  In common usage, "name" is often
used to refer to the "nnml:foo" string.  Sometimes the manual uses
"name" this way too.  I think the "nnml:foo" form is the more useful
identifier, since it's more informative and all servers are guaranteed
to have one.  Having an extra identifier doesn't provide any
additional functionality, and just causes confusion when the manual
calls it the "name".  I guess it would be a lot of work to get rid of
it, though.


paul



  reply	other threads:[~2002-05-20 19:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 19:58 Josh Huber
2002-05-03 11:17 ` Kai Großjohann
2002-05-03 15:26   ` Josh Huber
2002-05-03 17:47     ` Kai Großjohann
2002-05-03 18:39       ` Josh Huber
2002-05-05 11:56         ` Kai Großjohann
2002-05-07 14:28           ` Josh Huber
2002-05-07 14:34             ` Josh Huber
2002-05-07 15:22               ` Kai Großjohann
2002-05-07 16:31                 ` Josh Huber
2002-05-07 15:24             ` Kai Großjohann
2002-05-07 16:29               ` Josh Huber
2002-05-12 20:33             ` Raymond Scholz
2002-05-13 14:11               ` Josh Huber
2002-05-14 21:12                 ` Raymond Scholz
2002-05-15 14:36                   ` Josh Huber
2002-05-15 16:01                     ` Raymond Scholz
2002-05-15 17:21                       ` Josh Huber
2002-05-18 19:03                         ` Kai Großjohann
2002-05-20 14:08                           ` Josh Huber
2002-05-20 14:35                             ` Kai Großjohann
2002-05-20 18:34                               ` Josh Huber
2002-05-20 19:01                                 ` Kai Großjohann
2002-05-20 19:16                                   ` Paul Jarc [this message]
2002-05-20 20:08                                     ` Kai Großjohann
2002-05-20 21:32                                   ` Josh Huber
2002-05-21 10:44                                     ` Kai Großjohann
2002-05-21 12:48                             ` Raymond Scholz

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