From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Expiring Old Messaes
Date: 11 Nov 2000 11:43:59 +0100 [thread overview]
Message-ID: <vafbsvmzt3k.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <76puk3ip2t.fsf@newjersey.ppllc.com>
On 10 Nov 2000, Jake Colman wrote:
> I recently discovered the joys of auto-expiry and have configured a
> numbr of groups to auto-expire as needed. The problem is that some
> of these groups contain hundreds of read messages. How do I
> automagically mark them as expirable without manually marking or
> rereading them?
I'm afraid you have to mark them manually. Try setting
gnus-summary-goto-unread to nil, then you should be able to do `4 7 1
1 E' to mark 4711 articles as expirable. After marking as expirable,
you can then set gnus-summary-goto-unread back to the old value.
Hm.
Or does it work to say `4 7 1 1 M-x
gnus-summary-put-mark-as-expirable-next RET', regardless of the
variable value?
kai
--
The arms should be held in a natural and unaffected way and never
be conspicuous. -- Revised Technique of Latin American Dancing
prev parent reply other threads:[~2000-11-11 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 19:50 Jake Colman
2000-11-11 10:43 ` Kai Großjohann [this message]
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=vafbsvmzt3k.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).