Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Gnus <ding@gnus.org>
Subject: Re: spam.el binds too many keys to `gnus-summary-mark-as-spam'
Date: Mon, 31 Mar 2008 09:09:57 -0500	[thread overview]
Message-ID: <86ve33q91m.fsf@lifelogs.com> (raw)
In-Reply-To: <v91w5sh16d.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sun, 30 Mar 2008 14:00:10 +0200")

On Sun, 30 Mar 2008 14:00:10 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote: 

RS> `gnus-summary-mark-as-spam' is bound to M-d, S x, and M s x.  What a
RS> waste of key bindings!  ;-)

RS> (gnus-define-keys gnus-summary-mode-map
RS>   "St" spam-generic-score
RS>   "Sx" gnus-summary-mark-as-spam
RS>   "Mst" spam-generic-score
RS>   "Msx" gnus-summary-mark-as-spam
RS>   "\M-d" gnus-summary-mark-as-spam)

RS> I think each command (gnus-summary-mark-as-spam and
RS> spam-generic-score) should have only _one_ binding by default.  If the
RS> user wants a shorter one, (s)he can always use the user-reserved keys
RS> (Emacs: `C-c [A-Za-z]', Gnus: `v ...').

I think those keys were chosen by consensus because several people liked
different bindings.  I think `S x' should be the default, and
Mst/Msx/M-d should go away, but I really don't have strong feelings for
any of those key bindings.  I use C-s personally, FWIW, because it's
such a useful operation.

Ted



  reply	other threads:[~2008-03-31 14:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-30 12:00 Reiner Steib
2008-03-31 14:09 ` Ted Zlatanov [this message]
2008-04-01  8:44   ` Johan Bockgård
2008-04-20 12:32     ` Reiner Steib
2008-04-21 16:46       ` Ted Zlatanov
2008-04-21 17:06         ` Reiner Steib
2008-04-23 17:58           ` 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=86ve33q91m.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).