From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: gnus-summary-catchup-and-exit-AND-mark-as-expirable
Date: Mon, 09 Aug 2010 09:17:55 -0500 [thread overview]
Message-ID: <878w4f27l8.fsf@lifelogs.com> (raw)
In-Reply-To: <87zkx02y8l.fsf@jidanni.org>
On Fri, 06 Aug 2010 11:53:14 +0800 jidanni@jidanni.org wrote:
>> What binding do you propose?
j> I'll leave that to the pros.
TZ> There's auto-expire. So you're saying you want its effect sometimes
TZ> after you've read a group? It seems like something you should set once
TZ> per group and never worry about again. What kind of groups would you
TZ> want to auto-expire only sometimes? I can't think of any so I am not
TZ> eager to put such a binding into Gnus, but perhaps I'm not seeing it.
j> OK, it's those nnrss groups. There the ones that actually leave messages
j> on my disk. But I don't always want to expire them all the same way or
j> always the same way...
I think making this keybinding generally available will confuse users
who also look at total-expire and auto-expire (those two are confusing
enough alone). It's easy to write it yourself as a macro or a
function. I could be wrong, but I need at least one more vote in favor
of this feature to know I'm wrong :)
Ted
prev parent reply other threads:[~2010-08-09 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 23:14 gnus-summary-catchup-and-exit-AND-mark-as-expirable jidanni
2010-08-03 5:55 ` gnus-summary-catchup-and-exit-AND-mark-as-expirable Adam Sjøgren
2010-08-03 18:48 ` gnus-summary-catchup-and-exit-AND-mark-as-expirable Ted Zlatanov
2010-08-06 3:53 ` gnus-summary-catchup-and-exit-AND-mark-as-expirable jidanni
2010-08-09 14:17 ` Ted Zlatanov [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=878w4f27l8.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).