From: Michael Below <mbelow@antithese.de>
Subject: Customizing keys, was Re: Moving the spam around
Date: Fri, 07 Feb 2003 23:00:46 +0100 [thread overview]
Message-ID: <87smuz4upd.fsf_-_@antithese.de> (raw)
In-Reply-To: <87y94r4vy4.fsf@antithese.de>
Yet another followup question:
I would like to map my anti-spam-function to B r. How do I do that?
I couldn't find the name of the variable, so I tried something like
gnus-mode-map or the like:
(define-key gnus-overview-mode-map "Br" 'mb-gnus-raze-spam)
But these variables are not known. What is the right way to do this?
Michael
--
"Die Landesregierung steht gerne als Dienstleister für Nokia voll zur
Verfügung." -- Ministerpräsident Peer Steinbrück bei der
10-Jahres-Feier der deutschen Nokia-Niederlassung.
next parent reply other threads:[~2003-02-07 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87fzqzeqcn.fsf@antithese.de>
[not found] ` <87y94r4vy4.fsf@antithese.de>
2003-02-07 22:00 ` Michael Below [this message]
[not found] ` <m37kcav7bd.fsf@quimbies.gnus.org>
2003-02-08 23:03 ` Michael Below
2003-02-07 23:57 ` Oliver Enzmann
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=87smuz4upd.fsf_-_@antithese.de \
--to=mbelow@antithese.de \
/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).