From: Nevin Kapur <nevin@jhu.edu>
Subject: Re: [PATCH] Make gnus-summary-delete-article respect group parameters
Date: Tue, 09 Jul 2002 09:09:29 -0400 [thread overview]
Message-ID: <m3it3p6oae.fsf@fermat.mts.jhu.edu> (raw)
In-Reply-To: <ilusn2tawlc.fsf@latte.josefsson.org> (Simon Josefsson's message of "Tue, 09 Jul 2002 14:56:31 +0200")
Simon Josefsson <jas@extundo.com> writes:
> Nevin Kapur <nevin@jhu.edu> writes:
[...]
>> I would also like to argue that B DEL performing expiry instead of
>> deletion is inconsistent with its name and its description in the
>> manual.
>
> Yes, which is why B DEL doesn't respect expiry-target, no?
But it respects nnmail-expiry-target. So if you have it set to
something other than 'delete, then any article that is B DELed will be
put through the expiry process. In my case that means junk mail that
makes it to my INBOX lands up in my archive groups.
> If you want expiry-target to be adheared, you should expire the
> article, not delete it.
With the current behavior it is not possible to have
nnmail-expiry-target set to some archival sort of function *and* have
B DEL immediately expunge the article, bypassing nnmail-expiry-target.
I offered the patch to make the current behavior consistent. If
g-s-d-a looks at nnmail-expiry-target then it should also look at the
expiry-target group parameter.
For me the best outcome would be if B DEL outright deleted the
article. But this may break somebody else's setup who has relied on B
DEL to expire articles. For them the patch is useful.
> Perhaps this isn't a intuitive default behaviour, I'm not sure since I
> don't use expiry-target.
I don't know how to change the default behavior in a nice backward
compatible way. Once could always introduce another variable...
-Nevin
next prev parent reply other threads:[~2002-07-09 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 12:32 Nevin Kapur
2002-07-09 12:56 ` Simon Josefsson
2002-07-09 13:09 ` Nevin Kapur [this message]
2002-07-09 13:18 ` Simon Josefsson
2002-07-11 11:36 ` Steve Youngs
2002-07-26 12:24 ` Simon Josefsson
2002-07-26 15:10 ` Benjamin Rutt
2002-07-26 16:34 ` Simon Josefsson
2002-08-02 10:51 ` Steve Youngs
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=m3it3p6oae.fsf@fermat.mts.jhu.edu \
--to=nevin@jhu.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).