From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: self contained nnfolder
Date: Sun, 02 Sep 2001 19:54:02 -0400 [thread overview]
Message-ID: <m3ae0dp2rz.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <87ofotfv4x.fsf@uwo.ca> (Dan Christensen's message of "Sun, 02 Sep 2001 11:51:58 -0400")
Dan Christensen <jdc+news@uwo.ca> wrote:
> prj@po.cwru.edu (Paul Jarc) writes:
>> gnus-secondary-select-methods should
>> also be nil, or, if you want your foreign nnfolder server to also be
>> secondary, use '("nnfolder:").
>
> This didn't work. I got an error that "nnfolder:" wasn't a list.
Hm. Well, do you really need it to be both foreign and secondary?
If it's foreign only, then Gnus won't check it for new groups, I
think. If it's secondary only, then you have to change it by editing
your .gnus, not in the *Server* buffer.
> So I've set gnus-secondary-select-methods to ((nnfolder "")). Will
> this cause me some problems?
I'm not sure. But that's what it was when you started, right? So at
least you wan't be any worse off.
>> Edit your .newsrc.eld (while Gnus is
>> not running) to remove whichever entry from gnus-server-alist you
>> don't want to use.
>
> I don't want to use "archive", but when I removed it from
> gnus-server-alist I got an error message when Gnus started, even
> though the string `archive' didn't appear anywhere in my .newsrc.eld
> or my .gnus.
I should have said that you shouldn't try restarting Gnus at this
point - you also need to fix gnus-message-archive-method first.
> I've got it set to (nnfolder "").
Looking at the code now, the default seems to be "archive", wihchi is
a server name, so "nnfolder:" ought to work.
So if you quit Gnus, set g-m-a-m, edit .newsrc.eld so
gnus-server-alist uses the "" name and not "archive", and restart
Gnus, then does it work?
paul
next prev parent reply other threads:[~2001-09-02 23:54 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
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 [this message]
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=m3ae0dp2rz.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).