From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: auto auto-expirable
Date: Tue, 02 Jun 2009 19:34:53 +0200 [thread overview]
Message-ID: <8763fesfnm.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <12651.1243909393@rawbw.com>
On Tue, Jun 02 2009, Mike Kupfer wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> :variable gnus-auto-auto-expirable-newsgroups
>> :variable-default nil
>> :variable-document
>> "Groups in which articles that have been read are automatically
>> marked as expirable when moved to or copied to there.
>
> "Articles that are moved or copied into these groups will retain
> the expirable mark.
Does your proposal only apply to auto-expirable groups/articles? The
variable names and Katsumi's doc strings suggest it, but according
to Mike's doc string suggestion, it applies to all expirable article.
On Tue, Jun 02 2009, Katsumi Yamaoka wrote:
> (defcustom gnus-inhibit-auto-auto-expiry nil
> "If non-nil, don't do auto auto-expiry when moving or copying articles.
> `Auto auto-expiry' means that read articles, even if they haven't been
> marked as expirable, will be automatically marked as expirable when
> moved or copied to a group in which to perform auto-expiry."
I don't have a good suggestion, but the term `Auto auto-expiry' (and
the variable names *-auto-auto-*) is not clear.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2009-06-02 17:34 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
2009-06-13 14:22 ` Tim Landscheidt
2009-08-12 8:28 ` Katsumi Yamaoka
2009-06-02 17:34 ` Reiner Steib [this message]
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=8763fesfnm.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.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).