Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Strange server names confusion
Date: Sun, 02 Sep 2001 12:44:14 +0200	[thread overview]
Message-ID: <vafzo8dna81.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3ofounqdr.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Sun, 02 Sep 2001 00:54:50 -0400")

prj@po.cwru.edu (Paul Jarc) writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> > Simon Josefsson <jas@extundo.com> writes:
>>> Foreign groups are identified by the name of the server (car of each
>>> entry in `gnus-server-alist').
>> 
>> And secondary groups are identified in some other way?
>
> Here's the story AIUI.  Every select method has a first element (the
> backend) and a second element (which you and I might have thought of
> as the "name" but which Gnus calls the "address").  Some select
> methods (the primary and foreign ones) also have "server names".  The
> primary select method's name is "native", and a foreign method's name
> is its key in gnus-server-alist.  Secondary select methods do not have
> "server names".

Is there a way for a foreign server to have a different name than
address using the `normal' Gnus functions?  Or do I have to frob
gnus-server-alist directly for that?

>> Does this mean I can have two secondary servers with the same name (as
>> long as the backend is different), but not two foreign servers with
>> the same name?
>
> You can have two servers of any kind with the same "address" if they
> have different backends.  You cannot have two servers of any kind with
> the same "name".  I think.

Okay, I think I got that.  Since secondary servers don't have names,
it's not a problem to have both (nnml "" ...) and (nnimap ""...).

>> Well, I tried to enter "nntp:quimby" (with quotes) after `G e' on the
>> group, then I tried to enter the group -- no dice.  But with "quimby"
>> (with quotes), it worked.
>
> I think "nntp:quimby.gnus.org" would work, assuming "quimby.gnus.org"
> is the second element of your select method.

I have the following entry in gnus-server-alist:

("quimby" nntp "quimby" (nntp-address "news.gnus.org"))

I think that this means that both the name and the address are
"quimby".  Therefore, "nntp:quimby" should work.  But it doesn't, only
"quimby" works.

Or are you saying that with the above entry, "nntp:news.gnus.org"
should work?  Whee...

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


  reply	other threads:[~2001-09-02 10:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-01 19:06 Kai Großjohann
2001-09-01 19:39 ` Simon Josefsson
2001-09-01 21:59   ` Kai Großjohann
2001-09-02  4:54     ` Paul Jarc
2001-09-02 10:44       ` Kai Großjohann [this message]
2001-09-02 23:13         ` Paul Jarc
2001-09-03  8:23           ` Simon Josefsson
2001-09-03 14:17             ` Kai Großjohann
2001-09-03 23:04               ` Paul Jarc
2001-09-04 13:44                 ` Kai Großjohann
2001-09-05  0:55                   ` Paul Jarc
2001-09-04  0:05             ` Paul Jarc
2001-09-03 10:21           ` Kai Großjohann

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