Gnus development mailing list
 help / color / mirror / Atom feed
From: Mike Kupfer <mike.kupfer@xemacs.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: auto auto-expirable
Date: Wed, 03 Jun 2009 21:13:54 -0700	[thread overview]
Message-ID: <20134.1244088834@rawbw.com> (raw)
In-Reply-To: Your message of "Tue, 02 Jun 2009 20:12:04 +0900." <b4mk53u7uuz.fsf@jpl.org>

I like the gnus-inhibit-auto-auto-expiry user option.

>>>>> "KY" == Katsumi Yamaoka <yamaoka@jpl.org> writes:

KY> It never slows Gnus, though it doesn't provide the means to
KY> customize the behavior group by group.

For my purposes at least, that's not a problem.  I don't expect to
customize the behavior on a per-group basis.

KY> BTW, here is another solution, that lets Gnus behave as before even
KY> if the patch that I made has been applied.  Though it might make
KY> moving and copying of articles slow if the target group contains
KY> 100,000 articles.  Isn't it acceptable?

I could certainly live with a hook like this, especially since you've
written it for me :-), though I think I'd prefer the
gnus-inhibit-auto-auto-expiry user option.

cheers,
mike



  parent reply	other threads:[~2009-06-04  4:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 11:19 Katsumi Yamaoka
2009-05-29 12:08 ` Didier Verna
2009-06-01  3:36 ` Mike Kupfer
2009-06-01  8:35   ` Didier Verna
2009-06-01 11:20     ` Katsumi Yamaoka
2009-06-01 12:47       ` Tim Landscheidt
2009-06-02  2:23       ` Mike Kupfer
2009-06-02 11:12         ` Katsumi Yamaoka
2009-06-02 11:38           ` Katsumi Yamaoka
2009-06-04  4:13           ` Mike Kupfer [this message]
2009-06-13 14:22           ` Tim Landscheidt
2009-08-12  8:28             ` Katsumi Yamaoka
2009-06-02 17:34         ` Reiner Steib
2009-06-05 12:34       ` Greg Troxel

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=20134.1244088834@rawbw.com \
    --to=mike.kupfer@xemacs.org \
    --cc=ding@gnus.org \
    --cc=yamaoka@jpl.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).