From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: merlyn@stonehenge.com
Subject: Re: nnfolder: seems broken out of the box on 5.8.8
Date: 17 Mar 2001 00:30:33 +0100 [thread overview]
Message-ID: <vafofv18f6u.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m37l1p73sx.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "16 Mar 2001 17:21:28 -0500")
On 16 Mar 2001, Paul Jarc wrote:
> 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.
Maybe nnmh has the advantage that you can just drop a file into a
directory and lo! you have saved a message. Gnus uses this to ensure
that auto-saved messages are automatically stored in the draft folder.
If this wasn't the case, the method for auto-saving the current buffer
would have to be changed for message buffers.
Alas, Gnus doesn't auto-grok auto-saved messages. You have to
manually rename the file from #42# to 42. Oh, well. I think I
reported this bug, so it might be fixed by now, but I'm too lazy to
look right now -- it's almost time to hit the sack.
kai
--
Be indiscrete. Do it continuously.
next prev parent reply other threads:[~2001-03-16 23:30 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
2001-03-16 22:31 ` Randal L. Schwartz
2001-03-16 23:30 ` Kai Großjohann [this message]
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=vafofv18f6u.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=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).