Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: automatically set expiry mark
Date: Wed, 21 Dec 2011 19:29:07 +0100	[thread overview]
Message-ID: <87ipl9ixsc.fsf@dod.no> (raw)
In-Reply-To: <87d3bh25ug.fsf@ucl.ac.uk>

>>>>> Eric S Fraga <e.fraga@ucl.ac.uk>:

> ,----
> | [X] Automatic Expire
> |     All articles that are read will be marked as expirable.
> | 
> | [X] Expire Wait: [Value Menu] 14
> |     When to expire. More
> `----

Note: "Automatic Expire" and "Total Expire" (that I suggested) are two
different ways of achieving exipry of read articles.

With "Automatic Expire" the articles are marked as E when you read
them (I think...?  I've never tried it...).

With "Total Expire" read articles are marked as O, and when expiring all
articles marked O, are candidates for expiry.




  reply	other threads:[~2011-12-21 18:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-21 13:49 Carson Chittom
2011-12-21 17:27 ` Eric S Fraga
2011-12-21 18:29   ` Steinar Bang [this message]
2011-12-22 14:05   ` Carson Chittom
2011-12-22 14:22     ` Steinar Bang
2011-12-21 18:20 ` Steinar Bang

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=87ipl9ixsc.fsf@dod.no \
    --to=sb@dod.no \
    --cc=ding@gnus.org \
    /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).