From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: B DEL is being treated as expiry?
Date: Tue, 23 Jul 2002 13:40:14 -0400 [thread overview]
Message-ID: <m3ptxeuyuj.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vxklm82fke4.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "Tue, 23 Jul 2002 13:01:55 -0400")
Karl Kleinpaste <karl@charcoal.com> wrote:
> gnus-summary-delete-article is intended to delete articles, period.
Right.
> My 1-line fix makes it do that, again, for both the non-default
> nnmail-expiry-target case as well as the group parms expiry-target
> case.
But only by chance, and only for certain backends. The backend
interface must define how this is expressed, and all backends must be
made to conform to that specification. g-s-d-a is not supposed to
know the details of how backends decide what to do with expirable
articles; it's only supposed to know what to pass to
nnchoke-request-expire-articles.
> If you have other issues, such as nnmaildir not coping, then you have
> a problem specific to that, needing a bugfix for nnmaildir.
The problem isn't specific to nnmaildir; your fix is specific to
nnmail-derived backends. I don't know, but I'd guess that it also
fails for nnimap.
> And if an -expire-article-right-now function is wanted, that is a
> separate question, completely disjoint from whether -delete-article
> works.
It isn't completely disjoint, because it's likely that we'll want to
use the same backend function for both purposes. (Otherwise we'll be
duplicating a significant amount of code.) So the interface for that
function must define how the two cases are distinguished.
> You may have a design issue related to how to do that, but my bugfix
> takes care of the outright flaw of -delete-article so that it works
> properly.
No, it only makes the symptom disappear for cases like yours.
paul
next prev parent reply other threads:[~2002-07-23 17:40 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 [this message]
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
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=m3ptxeuyuj.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).