From: merlyn@stonehenge.com (Randal L. Schwartz)
Subject: nnfolder: seems broken out of the box on 5.8.8
Date: 14 Mar 2001 10:39:49 -0800 [thread overview]
Message-ID: <m11ys0gpoq.fsf@halfdome.holdit.com> (raw)
I've never used nnfolder before, although it seems to get recreated
even when I try to get rid of all traces of it.
I have no nnfolder- settings in my .gnus.el
When I eradicate any trace of what was previously set up, I get
~/Mail/archive/ created, empty, and the following settings
get copied into my servers:
(nnfolder "archive"
(nnfolder-directory "~/Mail/archive")
(nnfolder-active-file "~/Mail/archive/active")
(nnfolder-get-new-mail nil)
(nnfolder-inhibit-expiry t))
And these look to be the current values of those variables as well.
When I use "G m" to make "testing" in "nnfolder:", I get a file
named ~/Mail/testing, and ~/Mail/active gets updated. This seems contrary
to the settings above.
And in fact, when I then browse the server from the servers, I get
no groups again.
Shouldn't it be ~/Mail/archive/testing and shouldn't it touch
~/Mail/archive/active, and not mix that with my nnml: active file?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next reply other threads:[~2001-03-14 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-14 18:39 Randal L. Schwartz [this message]
2001-03-14 18:51 ` ShengHuo ZHU
2001-03-16 22:21 ` Paul Jarc
2001-03-16 22:31 ` Randal L. Schwartz
2001-03-16 23:30 ` Kai Großjohann
2001-03-19 19:28 ` gnus-draft-group? (was: nnfolder: seems broken) Paul Jarc
2001-03-19 19:41 ` Kai Großjohann
2001-03-19 19:48 ` Paul Jarc
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=m11ys0gpoq.fsf@halfdome.holdit.com \
--to=merlyn@stonehenge.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).