From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: followups go to expired group
Date: 07 Feb 2001 16:03:35 -0500 [thread overview]
Message-ID: <5bk872fbo8.fsf@avocet.cs.rochester.edu> (raw)
In-Reply-To: <rpv3ddq1b1m.fsf@django.timesten.com> (David Aspinwall's message of "07 Feb 2001 12:40:53 -0800")
David Aspinwall <aspinwall@TimesTen.com> writes:
> I use
> (setq nnmail-expiry-target "nnml:expired")
> so that expired messages go to a 'expired' group. I also use
> (: nnmail-split-fancy-with-parent)
> in nnmail-split-fancy, so that followup messages go to the same group
> as their parents. The unfortunate effect of this is that if someone
> replies to a message which has already expired, the reply goes to the
> 'expired' group. I pretty much never look at that group, so I usually
> don't even notice the new message.
>
> Is there any way to get (: nnmail-split-fancy-with-parent) to work
> except when the parent has been expired? I guess I could move it from
> the '(|' section of nnmail-split-fancy to the '(&' section so it gets
> cross-posted, but I don't normally want that.
It could be done by disabling nnmail-cache-accepted-message-ids when
expire articles. If no one opposes it, I'll put it into oGnus. Before
that, you can defadvice nnmail-expiry-target-group.
ShengHuo
--
(setq gnus-posting-styles
'((".*" (signature (format "(setq gnus-posting-styles
'%S)" gnus-posting-styles)))))
prev parent reply other threads:[~2001-02-07 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 20:40 David Aspinwall
2001-02-07 21:03 ` ShengHuo ZHU [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=5bk872fbo8.fsf@avocet.cs.rochester.edu \
--to=zsh@cs.rochester.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).