Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: draft on imap?
Date: Mon, 04 Oct 2010 11:28:46 -0500	[thread overview]
Message-ID: <87eic5exc1.fsf@lifelogs.com> (raw)
In-Reply-To: <87vd5ify7p.fsf@gmail.com>

On Mon, 04 Oct 2010 12:12:10 +0900 Bruno Tavernier <tavernier.bruno@gmail.com> wrote: 

BT> Is there a way to store drafts on an IMAP server?
BT> It is sometime useful when writing a long message or realizing that a
BT> file to be attached is not on the current computer, etc.

BT> I tried to do something like:
BT> 1) Write a uncomplete message and save it
BT> 2) Move/Copy from nndraft to a .draft folder on my IMAP server
BT> 3) Go to the .draft folder and gnus-article-edit -> 
BT> "gnus-article-edit: The current newsgroup does not support article editing"

BT> Note, we circumvent the lack of editing by:
BT> 4) from .draft folder, move/copy to nndraft:drafts
BT> 5) got to nndraft:drafts and edit

BT> That still is very dirty approach.

BT> That would be really cool, to be able to save/edit directly from the
BT> IMAP server. Is there any such a feature planned?

There's a whole lot of complicated code around drafts.  I think it would
be nice if any dedicated writeable group X (including nnimap) that
supports deletion could contain drafts, and the user could say "draft
group for this group/topic/server is X."  But there's been literally
hundreds of bugs and minor issues with nndraft over the years so I think
a full rewrite is the best way to make it work perfectly.  The point is
that such a rewrite would make drafts work with nnimap or any other
backend.

Regarding nnimap article editing, I think Lars is in vague agreement
that it's a good feature but it's not high on his priority list.  I
personally use the move-edit-move approach you suggested and look
forward to native editing.

Ted




      reply	other threads:[~2010-10-04 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04  3:12 Bruno Tavernier
2010-10-04 16:28 ` Ted Zlatanov [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=87eic5exc1.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).