From: prj@po.cwru.edu (Paul Jarc)
Cc: ding@gnus.org
Subject: Re: nnfolder: seems broken out of the box on 5.8.8
Date: 16 Mar 2001 17:21:28 -0500 [thread overview]
Message-ID: <m37l1p73sx.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <m11ys0gpoq.fsf@halfdome.holdit.com> (merlyn@stonehenge.com's message of "14 Mar 2001 10:39:49 -0800")
merlyn@stonehenge.com (Randal L. Schwartz) writes:
> I've never used nnfolder before, although it seems to get recreated
> even when I try to get rid of all traces of it.
If you mean ~/Mail being recreated, I think that's because of nndraft.
WIBNI if we could do something like:
(setq gnus-draft-group "nnfoo:group.name")
where nnfoo would be any backend that supports the necessary
operations? Then we wouldn't need an extra backend solely for drafts.
Or is nndraft too unlike any other backend? It derives from nnmh, so
I wouldn't think it would be impossibly different.
paul
next prev parent reply other threads:[~2001-03-16 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-14 18:39 Randal L. Schwartz
2001-03-14 18:51 ` ShengHuo ZHU
2001-03-16 22:21 ` Paul Jarc [this message]
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=m37l1p73sx.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=ding@gnus.org \
/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).