From: Carson Chittom <carson.chittom@mspb.ms.gov>
To: ding@gnus.org
Subject: Re: automatically set expiry mark
Date: Thu, 22 Dec 2011 08:05:27 -0600 [thread overview]
Message-ID: <4pwr9oem6w.fsf@mspb.ms.gov> (raw)
In-Reply-To: <87d3bh25ug.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Carson Chittom <carson.chittom@mspb.ms.gov> writes:
>> What I'd like to do is automatically mark read messages in my Inbox as
>> expired, so I don't periodically have to go through and mark, say, a
>> hundred of them manually. Is this possible? I looked in the manual at
>> what seemed likely in the index, but nothing popped out at me.
>
> If you type "G c" in the *Group* buffer for the Inbox group, you can
> adjust settings to do what you want. In particular, look for:
>
> ,----
> | [X] Automatic Expire
> | All articles that are read will be marked as expirable.
> |
> | [X] Expire Wait: [Value Menu] 14
> | When to expire. More
> `----
Where is this saved if the interface is used? I'd rather put it in with
all the rest of my Gnus configuration. Am I reading the manual
correctly that this is equivalent to putting the following in ~/.gnus.el?
,-----
| (setq gnus-parameters
| '(("nnimap+MSPB:Inbox"
| (auto-expire . t)
| (expiry-wait . 14))))
`-----
As I read it, the difference between auto-expire and total-expire is
that the former only marks read articles as expirable (and they are then
expired according to expiry-wait or nnmail-expiry-wait), whereas the
latter immediately expires read articles (either deleting them, or if
set up, moving them to the place specified by expiry-target or
nnmail-expiry-target). Is that correct?
next prev parent reply other threads:[~2011-12-22 14:05 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
2011-12-22 14:05 ` Carson Chittom [this message]
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=4pwr9oem6w.fsf@mspb.ms.gov \
--to=carson.chittom@mspb.ms.gov \
--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).