From: mdb@cdc.noaa.gov (Mark Borges)
Subject: Re: nnmail-expiry-wait-function: broke, or how-to?
Date: Mon, 4 Dec 1995 15:35:21 -0700 [thread overview]
Message-ID: <9512042235.AA14007@charney.cdc.noaa.gov> (raw)
In-Reply-To: steve@miranova.com's message of 04 Dec 1995 13:29:45 -0800
>> On 04 Dec 1995 13:29:45 -0800,
>> Steven L Baur(sb) wrote:
sb> nnmail-expiry-wait-function is called with a newsgroup name sans method.
sb> (setq nnmail-expiry-wait-function (lambda (group)
sb> (cond
sb> ((string= "nnml:lists.zsh" group)
sb> 30)
sb> Replace the comparison with:
sb> ((string= "lists.zsh" group)
sb> and you'll be O.K. The example in the manual shows something like
sb> this without commentary, perhaps it should say something explicit.
It doesn't seem to matter -- it appears to work fine with the method
left in. Should it? Lars?
sb> In order for expiration to occur, you must manually set the expired
sb> mark with the ``E'' command in the *Summary* buffer.
Hmm, after Robert's mail prompted me to set the variable `g-a-e-n', I
get the `E' mark automatically set now after I read the article if I
set it thusly,
------------------------------------------------------------------------------
gnus-auto-expirable-newsgroups's value is "nnml:lists\\.*"
Documentation:
*Groups in which to automatically mark read articles as expirable.
If non-nil, this should be a regexp that should match all groups in
which to perform auto-expiry. This only makes sense for mail groups.
------------------------------------------------------------------------------
(BTW, do I need another (or less) backwhack? I'm trying to match the
string nnml:lists.*, where `.' and `.' are literal.)
But note that it is not "retro-active", in that I have to expose all
the old articles and read or mark them to expire them.
Anyway, thanks for the help.
-mb-
next prev parent reply other threads:[~1995-12-04 22:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-13 16:17 Those groups levels again Lars Magne Ingebrigtsen
1995-11-13 19:50 ` Stainless Steel Rat
1995-11-13 20:58 ` Felix Lee
1995-11-13 22:48 ` Lars Magne Ingebrigtsen
1995-11-13 23:06 ` Scott Blachowicz
1995-11-13 23:15 ` Stainless Steel Rat
1995-11-18 6:49 ` Lars Magne Ingebrigtsen
[not found] ` <gvx91lext3f.fsf@plymouth.pilgrim.umass.edu>
1995-11-19 7:43 ` Lars Magne Ingebrigtsen
1995-11-20 16:43 ` Jack Vinson
1995-11-13 20:19 ` Joe Hildebrand
1995-11-13 20:21 ` Janne Sinkkonen
1995-11-18 6:49 ` Lars Magne Ingebrigtsen
1995-12-04 20:22 ` nnmail-expiry-wait-function: broke, or how-to? Mark Borges
1995-12-04 21:29 ` Steven L. Baur
1995-12-04 22:35 ` Mark Borges [this message]
1995-12-05 9:55 ` Lars Magne Ingebrigtsen
1995-12-04 22:09 ` Robert Pluim
1995-12-04 22:43 ` Mark Borges
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=9512042235.AA14007@charney.cdc.noaa.gov \
--to=mdb@cdc.noaa.gov \
/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).