Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: self contained nnfolder
Date: Sun, 02 Sep 2001 02:34:53 -0400	[thread overview]
Message-ID: <m3g0a6nlr0.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <87elpqikdi.fsf@uwo.ca> (Dan Christensen's message of "Sat, 01 Sep 2001 19:03:53 -0400")

Dan Christensen <jdc@uwo.ca> wrote:
> I'm still curious why my nnfolder groups come with various servers:
> "nnfolder:", (nnfolder "") and "archive".  What's the difference
> between these?

"nnfolder:" and "archive" are both strings identifying your
(nnfolder "") method; see my response to Kai.  The method itself
should always be specified in full (i.e., including all server
parameters) whenever it is used, but it should only be used once, in
one of gnus-select-method, gnus-secondary-select-methods, or
gnus-server-alist.  All other places that identify your server should
use one of the string forms.  A string form should also be used in
gnus-secondary-select-methods if the method is already in
gnus-server-alist (i.e., it's foreign).

Now maybe you're wondering which form of string identifier to use.
The advantage of "nnfolder:" is that it works for all kinds of servers
(primary, secondary, and foreign).  But if you commit to using a
foreign server, you can use the "archive" or "" name; the advantage
there is that you can change the select method's address (the string
after the backend), and the "archive" or "" name will still work.
(You can avoid the need for this, though, by explicitly using
whichever server parameter corresponds to the address, if any - e.g.,
nntp-address.)  The "nnfolder:" identification would have to be
updated to use the new address.  Conceivably, you might even be able
to change the foreign method's backend and still use the same
"archive" name, but there might well be problems with that.

> Can they be unified?  Is there a problem keeping them separate?  All
> the files are stored in one directory, and my server buffer only
> shows one nnfolder server.

I think you have only one select method, as far as Gnus is concerned.
You're specifying it in multiple places, though, which I imagine might
cause some trouble, especially if you ever change some server
parameters, so it'd be good to remove all but one, or replace them
with one of the string identifiers.

> A group created by moving an article to a non-existent group is
> created with the "archive" server.

I think that's because the "archive" name appears first in your
gnus-server-alist.  Gnus knows which method to put the group in, and
when it looks for the method's server name in gnus-server-alist,
"archive" is the first one it finds.


paul


  parent reply	other threads:[~2001-09-02  6:34 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-25 16:53 Simon Josefsson
2001-08-26 16:30 ` Raymond Scholz
2001-08-26 21:20   ` Simon Josefsson
2001-08-26 22:24     ` Nevin Kapur
2001-08-27  1:22       ` Steve Youngs
2001-08-27 16:19       ` Simon Josefsson
2001-08-27 16:36         ` Nevin Kapur
2001-09-01 22:22 ` Dan Christensen
2001-09-01 23:03   ` Dan Christensen
2001-09-01 23:31     ` Kai Großjohann
2001-09-02  6:34     ` Paul Jarc [this message]
2001-09-01 23:26   ` Kai Großjohann
2001-09-02  4:41     ` Dan Christensen
2001-09-02  6:11       ` Paul Jarc
2001-09-02 10:36         ` Kai Großjohann
2001-09-02 15:51         ` Dan Christensen
2001-09-02 16:48           ` Kai Großjohann
2001-09-02 23:58             ` Paul Jarc
2001-09-03  3:35             ` Dan Christensen
2001-09-03 10:16               ` Kai Großjohann
2001-09-03 15:07                 ` Dan Christensen
2001-09-03 16:31                   ` Kai Großjohann
2001-09-04  1:22                     ` Dan Christensen
2001-09-03 23:51                 ` Paul Jarc
2001-09-04  1:38                   ` Dan Christensen
2001-09-04  6:58                     ` Paul Jarc
2001-09-04 14:45                       ` Dan Christensen
2001-09-02 23:54           ` Paul Jarc
2001-09-03  3:49             ` Dan Christensen
2001-09-03 15:12               ` Dan Christensen
2001-09-03 23:36               ` Paul Jarc
2001-09-03 10:18             ` Kai Großjohann
2001-09-03 15:01               ` Dan Christensen
2001-09-03 15:22                 ` Dan Christensen
2001-09-03 16:34                   ` Kai Großjohann
2001-09-03 17:00                     ` Amos Gouaux
2001-09-03 21:31                       ` Kai Großjohann
2001-09-03 23:17                         ` Paul Jarc
2001-09-04  0:43                         ` Amos Gouaux
2001-09-04 13:41                           ` Kai Großjohann
2001-09-04 14:10                             ` Amos Gouaux
2001-09-03 23:23                   ` Paul Jarc
2001-09-04  1:14                     ` Dan Christensen
2001-09-04  1:33                     ` Dan Christensen
2001-09-04 13:42                     ` Kai Großjohann
2001-09-02  9:53   ` Simon Josefsson

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