From: Matt Armstrong <matt@lickey.com>
Subject: Re: Bug report: B c nnfolder:foo doesn't work
Date: Fri, 19 Oct 2001 18:32:14 -0600 [thread overview]
Message-ID: <87g08fjgmp.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <m3ofn3l4qq.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> Matt Armstrong <matt@lickey.com> wrote:
>> prj@po.cwru.edu (Paul Jarc) writes:
>>> What is your nnfolder server's nnfolder-directory server parameter,
>>> and What is your nnml server's nnml-directory server parameter? I
>>> think they both default to "~/Mail", which seems to be a bad thing.
>>
>> I have no nnfolder server. I have an nnfolder+archive server though.
>> Perhaps this is part of the problem?
>
> I meant your server belonging to the nnfolder backend, not one named
> "nnfolder".
I am confused by the distinction. How can I tell? I am mostly
confused by servers in Gnus.
I just performed another test. I can G c a new group and it appears
correctly in gnus-newsrc-alist:
("nnfolder:test-2"
(3 . 1)
((1 . 1))
nil
(nnfolder "")
((timestamp 15312 50110)))
And for the duration of the session I can use the group fine.
Then I exit and re-start Gnus. This bogus group is prepended to
gnus-newsrc-alist:
("test-2" 3 nil nil)
The original group remains, but is not visible in the group buffer.
("nnfolder:test-2"
(3 . 1)
((1 . 1))
nil
(nnfolder "")
((timestamp 15312 50110)))
And maybe this can help answer your original question?
(insert (pp gnus-opened-servers)) -->
(((nnfolder "")
ok)
((nndraft "")
ok)
((nnfolder "archive"
(nnfolder-directory "~/g/Mail/archive")
(nnfolder-active-file "~/g/Mail/archive/active")
(nnfolder-get-new-mail nil)
(nnfolder-inhibit-expiry t))
ok)
((nntp "news.speakeasy.net")
ok)
((nnml "")
ok))
--
matt
next prev parent reply other threads:[~2001-10-20 0:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 4:55 Matt Armstrong
2001-10-19 19:49 ` Paul Jarc
2001-10-19 20:58 ` Matt Armstrong
2001-10-19 21:05 ` Paul Jarc
2001-10-20 0:32 ` Matt Armstrong [this message]
2001-10-22 18:27 ` Paul Jarc
2001-10-19 21:08 ` Matt Armstrong
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=87g08fjgmp.fsf@squeaker.lickey.com \
--to=matt@lickey.com \
/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).