Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: gnus-draft-group? (was: nnfolder: seems broken)
Date: 19 Mar 2001 14:28:30 -0500	[thread overview]
Message-ID: <m31yrta77v.fsf_-_@multivac.cwru.edu> (raw)
In-Reply-To: <vafofv18f6u.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "17 Mar 2001 00:30:33 +0100")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> 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?
> 
> 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.

I think this could be generalized to any one-file-per-message backend.
When you start composing a message, Gnus would hand it to the backend
via nnfoo-request-accept-article.  Then we'd just have to add an
nnfoo-article-file-name function to the backend interface; Gnus would
use that to find out what file that article is stored in, and
associate the message buffer with that file.  Would that work?


paul


  reply	other threads:[~2001-03-19 19:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-14 18:39 nnfolder: seems broken out of the box on 5.8.8 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
2001-03-19 19:28     ` Paul Jarc [this message]
2001-03-19 19:41       ` gnus-draft-group? (was: nnfolder: seems broken) 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=m31yrta77v.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).