From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Binding of gnus-summary-expire-thread
Date: Thu, 27 Sep 2007 14:55:28 -0500 [thread overview]
Message-ID: <m2sl4zhoi7.fsf@lifelogs.com> (raw)
In-Reply-To: <v98x6snd94.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 27 Sep 2007 21:01:59 +0200")
On Thu, 27 Sep 2007 21:01:59 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote:
RS> On Thu, Sep 27 2007, Ted Zlatanov on ding-patches:
>> + (gnus-summary-mode-map, gnus-summary-thread-map): Add 'M-C-e' and 'T e'
>> + shortcuts for gnus-summary-expire-thread.
RS> [...]
>> @@ -1790,6 +1790,7 @@
>> "k" gnus-summary-kill-same-subject-and-select
>> "\C-k" gnus-summary-kill-same-subject
>> "\M-\C-k" gnus-summary-kill-thread
>> + "\M-\C-e" gnus-summary-expire-thread
>> "\M-\C-l" gnus-summary-lower-thread
>> "e" gnus-summary-edit-article
>> "#" gnus-summary-mark-as-processable
RS> This collides with the binding of `gnus-summary-edit-parameters':
RS> "\M-\C-e" gnus-summary-edit-parameters
RS> I think `T e' is sufficient, isn't it?
I was trying to provide parallels with M-C-k, and did not find an
existing M-C-e binding (I searched for M-C-e which was the wrong string
due to the backslashes, I now realize).
I'm OK with removing this in favor of `T e' but will wait for your
feedback on the alternate (`v' or `v e' or `C-c e' or none of those)
binding before making the change.
Ted
next prev parent reply other threads:[~2007-09-27 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Iaqxv-0001eS-00@quimby.gnus.org>
2007-09-27 19:01 ` Binding of gnus-summary-expire-thread (was: Changes committed gnus/lisp (ChangeLog gnus-sum.el)) Reiner Steib
2007-09-27 19:55 ` Ted Zlatanov [this message]
2007-09-27 21:25 ` Binding of gnus-summary-expire-thread Ted Zlatanov
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=m2sl4zhoi7.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).