From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: article editing in nnimap
Date: Wed, 22 Sep 2010 08:37:41 -0500 [thread overview]
Message-ID: <87pqw5hpay.fsf@lifelogs.com> (raw)
In-Reply-To: <m3hbhi4smh.fsf@quimbies.gnus.org>
On Wed, 22 Sep 2010 00:52:06 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Dan Christensen <jdc@uwo.ca> writes:
>> You'd need to transfer the marks over, right? Does `B m' do anything
>> else that would need to be done?
LMI> Yeah, marks... perhaps having a version of -copy-article that takes a
LMI> buffer as its argument in addition to the article number would be
LMI> easier? Then the marks would follow automatically.
I don't see (but perhaps I've missed it in the discussion) why not just
implement -replace-article (maybe it can use -copy-article internally)?
Then editing with `gnus-request-replace-article' will Just Work (with
`e' in the summary buffer for instance).
Ted
next prev parent reply other threads:[~2010-09-22 13:37 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
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 [this message]
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=87pqw5hpay.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).