From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: IMAP drafts
Date: Tue, 30 Dec 2003 02:29:56 +0100 [thread overview]
Message-ID: <m3ekunay97.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87ad5mgsdt.fsf@emptyhost.emptydomain.de>
Kai Grossjohann <kai@emptydomain.de> writes:
> Drafts are stored using the Emacs autosave mechanism, which saves
> files, not messages. One way to approach the problem would be to
> write a file handler (similar to Ange-FTP, say) that uses imap for
> storage. Then the message buffers could have an appropriate autosave
> name and then everything would Just Work.
That'd be very nice... It could even make sure that the MIME stuff
was properly formatted before stuffing the message into IMAP, etc.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-12-30 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3d6ai3273.fsf@1-1-1-8a.ras.sth.bostream.se>
[not found] ` <87ad5mgsdt.fsf@emptyhost.emptydomain.de>
2003-12-22 19:42 ` Mats Löfdahl
2003-12-30 1:29 ` Lars Magne Ingebrigtsen [this message]
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=m3ekunay97.fsf@quimbies.gnus.org \
--to=larsi@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).