From: mdb@cdc.noaa.gov (Mark Borges)
Cc: ding@ifi.uio.no
Subject: Re: Value for gnus-auto-expirable-newsgroups
Date: Tue, 5 Dec 1995 17:31:25 -0700 [thread overview]
Message-ID: <9512060031.AA23290@charney.cdc.noaa.gov> (raw)
In-Reply-To: Manoj Srivastava's message of 05 Dec 1995 17:48:07 -0500
>>>>> "M" == Manoj Srivastava <srivasta@pilgrim.umass.edu> writes:
M> Hi, Now that we know that nnmail-expiry-wait-function should
M> not contain the method ("other" rather than "nnml:other"), does
Do we? I thought it didn't matter:
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
Lars> mdb@cdc.noaa.gov (Mark Borges) writes:
>> It doesn't seem to matter -- it appears to work fine with the
>> method left in. Should it? Lars?
Lars> No, it shouldn't.
I took that as "it shouldn't matter".
M> it make sense to have gnus-auto-expirable-newsgroups set to
M> "^nnml:"?
That works for me, though I have "nnml:" in my wait function as well.
M> Or do I have to maintain the list by hand? Somewhare in thed
M> documentation I read that the forst element in the newsrc.eld
M> is the group name, and that certainly contains nnml: prefix.
The code has this (at least for Gnus-5.0.12, I haven't tried sgnus) in
gnus.el:
;; Check whether auto-expire is to be done in this group.
(setq gnus-newsgroup-auto-expire
(or (and (stringp gnus-auto-expirable-newsgroups)
(string-match gnus-auto-expirable-newsgroups group))
(memq 'auto-expire (nth 5 info))))
so it should be OK without the method, and (if group includes the
method, which I think it does) with the method as well.
-mb-
next prev parent reply other threads:[~1995-12-06 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gvx3fazxh3s.fsf@belthil.pilgrim.umass.edu>
1995-12-05 23:28 ` Thomas Neumann
1995-12-06 0:31 ` Manoj Srivastava
1995-12-06 0:31 ` Mark Borges [this message]
1995-12-06 2:01 ` Steven L. Baur
1995-12-06 5:05 ` Lars Magne Ingebrigtsen
1995-12-06 5:05 ` Lars Magne Ingebrigtsen
2002-10-20 20:17 Unknown
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=9512060031.AA23290@charney.cdc.noaa.gov \
--to=mdb@cdc.noaa.gov \
--cc=ding@ifi.uio.no \
/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).