From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: B DEL is being treated as expiry?
Date: Tue, 23 Jul 2002 17:43:50 -0400 [thread overview]
Message-ID: <m3wurmrufn.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <m3sn2a6suz.fsf@fermat.mts.jhu.edu> (Nevin Kapur's message of "Tue, 23 Jul 2002 17:23:48 -0400")
Nevin Kapur <nevin@jhu.edu> wrote:
> prj@po.cwru.edu (Paul Jarc) writes:
>> We want both functions available (delete immediately/expire
>> immediately), right?
>
> Do we really? Expiring immediately is almost a oxymoron. Expiry (as
> it works in Gnus) suggests something passive and deletion something
> active. I like Karl's patch. That's what I would like to see go
> through.
Regardless of whether we want immediate expiration, immediate deletion
should work for all backends; Karl's patch doesn't do that. Are there
any objections to using -request-move-article for deletion in
gnus-summary-delete-article ? I think that will work for all
backends.
Regarding immediate expiration, is that what
gnus-summary-expire-articles-now is supposed to do? Or should it
delete as well?
paul
next prev parent reply other threads:[~2002-07-23 21:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 11:21 Karl Kleinpaste
2002-07-23 11:49 ` Kai Großjohann
2002-07-23 13:40 ` Josh Huber
2002-07-23 13:58 ` Nevin Kapur
2002-07-23 16:03 ` Karl Kleinpaste
2002-07-23 16:16 ` Paul Jarc
2002-07-23 16:23 ` Karl Kleinpaste
2002-07-23 16:36 ` Paul Jarc
2002-07-23 17:01 ` Karl Kleinpaste
2002-07-23 17:40 ` Paul Jarc
2002-07-23 18:09 ` Karl Kleinpaste
2002-07-23 18:33 ` Paul Jarc
2002-07-24 15:44 ` Kai Großjohann
2002-07-24 16:05 ` Paul Jarc
2002-07-26 12:51 ` Simon Josefsson
2002-07-26 14:50 ` Paul Jarc
2002-07-26 16:37 ` Simon Josefsson
2002-07-26 16:48 ` Paul Jarc
2002-07-26 18:33 ` Simon Josefsson
2002-07-23 21:23 ` Nevin Kapur
2002-07-23 21:43 ` Paul Jarc [this message]
2002-07-24 2:08 ` Nevin Kapur
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=m3wurmrufn.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).