From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nnimap expiry
Date: Wed, 22 Sep 2010 13:25:42 -0500 [thread overview]
Message-ID: <87vd5xd49l.fsf@lifelogs.com> (raw)
In-Reply-To: <m3mxr9d6z3.fsf@quimbies.gnus.org>
On Wed, 22 Sep 2010 19:27:12 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>>> `B DEL' works to delete the article; I confirmed that nnimap-expunge
>>> doesn't make a difference to the issue noted above. So it looks like the
>>> gnus-expire flag used to become \Deleted in older Gnus after
>>> `gnus-summary-expire-articles-now' but now doesn't.
LMI> I don't think the expire flag makes any difference...
>> Sorry? I thought it would. Are you saying `B DEL' is the only way to
>> truly delete an article immediately now?
LMI> The expiry flag (per se) has never deleted anything. It only presents
LMI> candidates for deletion, and then you choose subsets of the
LMI> expiry-marked articles and then delete them. (Or all of them, in the
LMI> -now case.)
OK, to be clear, given a group with expirable (`E') articles, what do I
have to do in order to get them all deleted immediately?
Ted
next prev parent reply other threads:[~2010-09-22 18:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 18:01 Lars Magne Ingebrigtsen
2010-09-21 18:36 ` Robert Pluim
2010-09-21 18:56 ` Ted Zlatanov
2010-09-21 19:01 ` Lars Magne Ingebrigtsen
2010-09-22 13:02 ` Ted Zlatanov
2010-09-22 13:19 ` Ted Zlatanov
2010-09-22 16:40 ` Lars Magne Ingebrigtsen
2010-09-22 17:21 ` Ted Zlatanov
2010-09-22 17:27 ` Lars Magne Ingebrigtsen
2010-09-22 18:25 ` Ted Zlatanov [this message]
2010-09-22 18:38 ` Lars Magne Ingebrigtsen
2010-09-22 19:20 ` Ted Zlatanov
2010-09-22 19:28 ` Lars Magne Ingebrigtsen
2010-09-22 19:56 ` Ted Zlatanov
2010-09-22 20:08 ` Lars Magne Ingebrigtsen
2010-09-22 21:00 ` 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=87vd5xd49l.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).