From: Kai Grossjohann <grossjohann@charly.informatik.uni-dortmund.de>
Cc: ding@ifi.uio.no
Subject: Re: backgrounded expire deletes
Date: 07 Oct 1996 18:11:45 +0200 [thread overview]
Message-ID: <vaf3ezqvjni.fsf@ls6.informatik.uni-dortmund.de> (raw)
In-Reply-To: Wesley.Hardaker@sphys.unil.ch's message of 07 Oct 1996 16:21:03 +0100
>>>>> Wesley Hardaker writes:
Wes> I've thought for a long time, as I watch my stupid screen
Wes> saying 'deleting article XXX...' for a long time that it would
Wes> really cool to have all the deletions done at either a later
Wes> point or in the background.
Seems like these come from the expiry process. Here's what I use:
(remove-hook 'gnus-summary-prepare-exit-hook 'gnus-summary-expire-articles)
I have bound a convenient key in the *Group* buffer to
gnus-group-expire-all-groups. I hit this key every day before I go to
lunch.
Would that be a sloution?
kai
--
Life is hard and then you die.
next prev parent reply other threads:[~1996-10-07 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-07 15:21 Wesley.Hardaker
1996-10-07 16:11 ` Kai Grossjohann [this message]
1996-10-07 21:31 ` Colin Rafferty
1996-10-07 19:05 ` Ken Raeburn
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=vaf3ezqvjni.fsf@ls6.informatik.uni-dortmund.de \
--to=grossjohann@charly.informatik.uni-dortmund.de \
--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).