From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Expiry and nnimap: ghost articles
Date: Tue, 02 Oct 2001 13:46:55 -0400 [thread overview]
Message-ID: <m3itdyvsre.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <ilud74c5nad.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Thu, 27 Sep 2001 23:36:26 +0200")
Simon Josefsson <jas@extundo.com> wrote:
> Ah, yes -- if you move an article from a nnimap group to a nnfolder
> group (which was the case in this thread), moving doesn't happen
> within one backend, so Gnus does retrieve+delete.
Thinking more on this - even if Gnus does retrieve+delete, it could
(and ought to) use nnchoke-request-move-article to do it. Using
nnchoke-request-article is wrong, since it doesn't undo any changes
made by the backend, and using nnchoke-request-expire-articles is
wrong as has already been mentioned.
To retrieve with n-r-m-a, just pass nil as the accept-form; the
article will then be in the given buffer. To delete with n-r-m-a,
pass t as the accept-form. (Passing the destination backend's
-request-accept article would be even better, but might be a harder
change to make.)
paul
prev parent reply other threads:[~2001-10-02 17:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 0:17 Nevin Kapur
2001-09-26 7:31 ` Simon Josefsson
2001-09-26 16:56 ` Nevin Kapur
2001-09-26 17:56 ` Simon Josefsson
2001-09-26 21:10 ` Nevin Kapur
2001-09-27 8:43 ` Simon Josefsson
2001-09-27 14:41 ` Nevin Kapur
2001-09-27 15:54 ` Paul Jarc
2001-09-27 21:36 ` Simon Josefsson
2001-09-28 12:47 ` Kai Großjohann
2001-09-28 14:32 ` Nevin Kapur
2001-10-01 20:37 ` Paul Jarc
2001-10-02 17:50 ` Simon Josefsson
2001-10-02 17:46 ` Paul Jarc [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=m3itdyvsre.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).