From: Katsumi Yamaoka <yamaoka@jpl.org>
To: nils-dated-1213237429.39274f@ackermath.info
Cc: ding@gnus.org
Subject: Re: drafts and expiry-target problem and solution
Date: Wed, 19 Mar 2008 14:33:10 +0900 [thread overview]
Message-ID: <b4mve3juvl5.fsf@jpl.org> (raw)
In-Reply-To: <87abkv4kxm.fsf@aphrodite.localdomain>
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
>>>>> Nils Ackermann wrote:
> On second thought it appears to me that `message-disassociate-draft'
> shouldn't rely on `nnmh-request-expire-articles' to delete the mail
> from the drafts group. It should just delete it. Is there any deep
> reason for this choice?
I agree that `message-disassociate-draft' always deletes a draft
backup since it differs from a normal message, i.e., it has a
header separator, etc. But `nndraft-request-expire-articles',
that uses `nnmh-request-expire-articles', is easy to use because
it knows what draft to be deleted, I think. A corner-cutting way
is:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 510 bytes --]
--- nnmh.el~ 2008-03-18 22:47:32 +0000
+++ nnmh.el 2008-03-19 05:29:22 +0000
@@ -257,8 +257,10 @@
(nnmh-possibly-change-directory newsgroup server)
(let ((is-old t)
(nnmail-expiry-target
- (or (gnus-group-find-parameter newsgroup 'expiry-target t)
- nnmail-expiry-target))
+ (if (string-equal newsgroup "nndraft:drafts")
+ 'delete
+ (or (gnus-group-find-parameter newsgroup 'expiry-target t)
+ nnmail-expiry-target)))
article rest mod-time)
(nnheader-init-server-buffer)
[-- Attachment #3: Type: text/plain, Size: 528 bytes --]
>>> A quick grep through source (by parameter names) showed that there are
>>> many places where (general) group parameters aren't honored, even if
>>> they should be. Potentially this gives rise to a lot of bugs that
>>> seem unrelated. Probably there are also more places where the full
>>> group specification is missing in using `gnus-group-find-parameter'.
> This seems much more serious to me. I am considering helping to
> rectify this. Please instruct me about signing the papers.
Thanks. I sent a recipe to you.
prev parent reply other threads:[~2008-03-19 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r6eevweh.fsf@pascal.matem.unam.mx>
2008-03-18 12:53 ` Katsumi Yamaoka
2008-03-18 18:37 ` Reiner Steib
2008-03-18 22:59 ` Katsumi Yamaoka
2008-03-19 0:27 ` Nils Ackermann
2008-03-19 5:33 ` Katsumi Yamaoka [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=b4mve3juvl5.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=nils-dated-1213237429.39274f@ackermath.info \
/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).