Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: spam.el binds too many keys to `gnus-summary-mark-as-spam'
Date: Sun, 20 Apr 2008 14:32:05 +0200	[thread overview]
Message-ID: <v9y778iu62.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <yoijd4pa55ik.fsf@remote2.student.chalmers.se>

On Tue, Apr 01 2008, Johan Bockgård wrote:

> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I think those keys were chosen by consensus because several people
>> liked different bindings.  

If we'd use this policy ("several people like different bindings"), we
will end up with no available bindings very soon.

>> 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.

Thinking more about it, I think that the `S ...' bindings are
completely misplaced.  All other `S ...' are replying/posting related.

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

> I use $.

Me too.  ;-)

But I'm talking about the default key bindings which also occupy
bindings for users not using `spam.el' at all.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2008-04-20 12:32 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
2008-04-01  8:44   ` Johan Bockgård
2008-04-20 12:32     ` Reiner Steib [this message]
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=v9y778iu62.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).