From: John Palmieri <palmieri@math.washington.edu>
Subject: Re: Redefining keys in the pGnus summary buffer
Date: 21 Oct 1999 20:13:50 -0700 [thread overview]
Message-ID: <s5tvh805bpt.fsf@goedel2.math.washington.edu> (raw)
In-Reply-To: Daniel Pittman's message of "22 Oct 1999 11:03:55 +1000"
Daniel Pittman <daniel@danann.net> writes:
> I am having some trouble customizing the keyboard interface to pGnus
> ("Pterodactyl Gnus v0.96")
>
> What I want to do is redefine the keystroke M-k to lower the score of a
> thread. This is easy to do and I have it working.
>
> Getting the redefinition to happen automatically is a little harder
> however. I tried doing '(define-key gnus-summary-mode-map ...)' in .gnus
> and that didn't work -- I got the original binding.
>
> OK, I thought, and went hunting for where the keymap was frobnicated.
> 'gnus-sum.el' seemed to be the place that did it. So, I wrapped my
> redefinitions in an '(eval-after-load "gnus-sum" ...)' form.
>
> No joy. I still get the original key definition.
>
> So, can someone out there tell me where I am being stupid? I would like
> to be able to customize the keyboard interface quite a bit :)
I would expect that something like this would work, but I haven't
tried it:
(add-hook 'gnus-summary-mode-hook
'(lambda ()
(define-key gnus-summary-mode-map ...)))
(There are lots of "gnus-summary-BLAH-hook"s; gnus-summary-mode-hook
looks like it should work, but maybe you need
gnus-summary-generate-hook or gnus-summary-prepare-hook or one of the
other ones. Do M-x apropos-variable gnus-summary.*hook for a list.)
--
John H. Palmieri
Dept of Mathematics, Box 354350 palmieri@math.washington.edu
University of Washington http://www.math.washington.edu/~palmieri
Seattle, WA 98195-4350
next prev parent reply other threads:[~1999-10-22 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-22 1:03 Daniel Pittman
1999-10-22 3:13 ` John Palmieri [this message]
1999-10-22 15:34 ` Colin Rafferty
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=s5tvh805bpt.fsf@goedel2.math.washington.edu \
--to=palmieri@math.washington.edu \
/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).