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: Mon, 21 Apr 2008 19:06:27 +0200 [thread overview]
Message-ID: <v9lk37f88c.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <86abjnb1gg.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 21 Apr 2008 11:46:23 -0500")
On Mon, Apr 21 2008, Ted Zlatanov wrote:
> Maybe `,' (comma) would work?
comma is already taken: gnus-summary-best-unread-article
> I could get used to `,,' (comma + comma) for
> gnus-summary-mark-as-spam, and `,=' (comma + equals) for
> spam-generic-score. I don't know the Emacs + Gnus conventions,
> though, so this may be a bad idea.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2008-04-21 17:06 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
2008-04-21 16:46 ` Ted Zlatanov
2008-04-21 17:06 ` Reiner Steib [this message]
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=v9lk37f88c.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).