Gnus development mailing list
 help / color / mirror / Atom feed
From: pluim@xylint.co.uk (Robert Pluim)
Cc: ding@ifi.uio.no
Subject: Re: nnmail-expiry-wait-function: broke, or how-to?
Date: 04 Dec 1995 22:09:00 +0000	[thread overview]
Message-ID: <r220qkzdkz.fsf@basil.xylint.co.uk> (raw)
In-Reply-To: mdb@cdc.noaa.gov's message of Mon, 4 Dec 1995 13:22:56 -0700

>>>>> "Mark" == Mark Borges <mdb@cdc.noaa.gov> writes:
[correct setting of nnmail-expiry-wait-function deleted]

    Mark> But articles in my nnml mail folders are not being expired,
    Mark> e.g., I still have an (unticked) article dated 13 Nov in my
    Mark> lists.fvwm mail group, well beyond the 10 days I want to
    Mark> keep it. (BTW, will ticked articles be excluded from the
    Mark> expiry process?).

Are you explicitly marking the articles for expiry in the *Summary*
buffer by using 'E' ? (BTW ticked articles will be excluded, if by
ticked you mean marked using 'U')

    Mark> So either (a) I'm misunderstanding how this works, or (b)
    Mark> it's broke.  But it can't possibly be (b), so it must be
    Mark> (a).

It's (a), I think.

    Mark> Must I put gnus-group-expire-articles() on a hook function?
    Mark> If so, any suggestions on which one? Ideally, I'd like Gnus
    Mark> to assume auto-expiry of the groups I've gone to the trouble
    Mark> of listing in nnmail-expiry-wait-function, but I can do
    Mark> anything; I just need a bit more info.

You don't mention which version of ding you're using, but here goes
anyway.

You need to set gnus-auto-expirable-newsgroups to be a regexp which
matches the groups in which gnus will automatically *mark* articles
for expiry (note this is not the same as expiring them). You can then
expire articles in the group by using 'B e', or adding a hook,
probably to gnus-summary-prepare-exit-hook. (this is done by default
in some versions of ding)

See also the documentation for gnus-summary-prepare-exit-hook.

Hope this helps.

Robert


  parent reply	other threads:[~1995-12-04 22:09 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
1995-12-05  9:55       ` Lars Magne Ingebrigtsen
1995-12-04 22:09   ` Robert Pluim [this message]
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=r220qkzdkz.fsf@basil.xylint.co.uk \
    --to=pluim@xylint.co.uk \
    --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).