Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: article editing in nnimap
Date: Tue, 21 Sep 2010 23:30:09 +0200	[thread overview]
Message-ID: <m3zkva944e.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87vd6143w9.fsf@uwo.ca>

Dan Christensen <jdc@uwo.ca> writes:

> So I think it should be possible to re-use the code that is invoked when
> the user types `B m'.  An extra argument (or a global variable) could
> be used to tell nnimap-request-move-article that the move isn't
> to be considered internal and to tell nnimap-request-accept-buffer
> to take the article from the editing buffer.  That already would be
> a big step forward, but even better would be to update the summary
> buffer to replace the deleted article with the newly created article.

Well, calling -request-accept-article, and then deleting the old one
would sort of get you most of the way there, wouldn't it?
-request-accept-article returns the group/article number, so it'd kinda
be just

* request the article to a buffer
* call request-accept
* delete the previous article
* jump to the new article number in the summary buffer, which will request
the header for the "new" article.

Although you'd then have two entries in the thread with the same
Message-ID, which may freak out the threading code...  or not.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




  reply	other threads:[~2010-09-21 21:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20  1:09 Dan Christensen
2010-09-21 21:30 ` Lars Magne Ingebrigtsen [this message]
2010-09-21 22:24   ` Dan Christensen
2010-09-21 22:52     ` Lars Magne Ingebrigtsen
2010-09-21 23:01       ` Dan Christensen
2010-09-22 13:37       ` Ted Zlatanov
2010-09-22 16:49         ` Lars Magne Ingebrigtsen
2010-09-22 17:45         ` Dan Christensen

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=m3zkva944e.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --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).