From: Bruno Tavernier <tavernier.bruno@gmail.com>
To: ding@gnus.org
Subject: draft on imap?
Date: Mon, 04 Oct 2010 12:12:10 +0900 [thread overview]
Message-ID: <87vd5ify7p.fsf@gmail.com> (raw)
Is there a way to store drafts on an IMAP server?
It is sometime useful when writing a long message or realizing that a
file to be attached is not on the current computer, etc.
I tried to do something like:
1) Write a uncomplete message and save it
2) Move/Copy from nndraft to a .draft folder on my IMAP server
3) Go to the .draft folder and gnus-article-edit
->
"gnus-article-edit: The current newsgroup does not support article editing"
Note, we circumvent the lack of editing by:
4) from .draft folder, move/copy to nndraft:drafts
5) got to nndraft:drafts and edit
That still is very dirty approach.
That would be really cool, to be able to save/edit directly from the
IMAP server. Is there any such a feature planned?
--
Bruno
next reply other threads:[~2010-10-04 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 3:12 Bruno Tavernier [this message]
2010-10-04 16:28 ` Ted Zlatanov
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=87vd5ify7p.fsf@gmail.com \
--to=tavernier.bruno@gmail.com \
--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).