From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: gnus-summary-mark-thread-as-expirable
Date: Thu, 27 Sep 2007 23:07:02 +0200 [thread overview]
Message-ID: <v9hclfn7gp.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m2wsubhon1.fsf@lifelogs.com>
On Thu, Sep 27 2007, Ted Zlatanov wrote:
> On Thu, 27 Sep 2007 Reiner Steib <reinersteib+gmane@imap.cc> wrote:
> RS> On Thu, Sep 27 2007, Ted Zlatanov wrote:
>>> 3) if you like the behavior, you can map that to a key by itself, say
>>> C-e:
[...]
> RS> Better use `C-c e', `v' or `v e' as these are reserved for users.
> RS> `C-e' isn't.
>
> You decide, I'm OK with any one of those.
Uh, no. I wasn't talking about the default binding in Gnus here.
These are reserved for *users*.
> `T e' seems to be the best option anyhow.
We might use `T E': uppercase E in analogy to `E' for
`gnus-summary-mark-as-expirable' (and reserve `T e' for later). OTOH,
lowercase e in analogy to `M e'. I don't have strong opinion on this.
Both (`T E' and `T e') are fine with me.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2007-09-27 21:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 7:15 gnus-summary-mark-thread-as-expirable ecocode
2007-09-26 17:27 ` gnus-summary-mark-thread-as-expirable David Z Maze
2007-09-26 21:47 ` gnus-summary-mark-thread-as-expirable Ted Zlatanov
2007-09-27 6:02 ` gnus-summary-mark-thread-as-expirable ecocode
2007-09-27 10:56 ` gnus-summary-mark-thread-as-expirable Ted Zlatanov
2007-09-27 18:51 ` gnus-summary-mark-thread-as-expirable Reiner Steib
2007-09-27 19:52 ` gnus-summary-mark-thread-as-expirable Ted Zlatanov
2007-09-27 21:01 ` gnus-summary-mark-thread-as-expirable David Z Maze
2007-09-27 21:07 ` Reiner Steib [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=v9hclfn7gp.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).