From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: gnus keymap elisp confusion
Date: Tue, 08 Apr 2014 10:47:05 +0900 [thread overview]
Message-ID: <b4mob0c7fty.fsf@jpl.org> (raw)
In-Reply-To: <87zjjw62ci.fsf@treetowl.lan>
Ian Kelling wrote:
> nnmairix.el has this code:
> (defun nnmairix-group-mode-hook ()
> "Nnmairix group mode keymap."
> (define-key gnus-group-mode-map
> (kbd "G b") (make-sparse-keymap))
> (define-key gnus-group-mode-map
> (kbd "G b g") 'nnmairix-create-search-group)
> ...
> The keybinds work fine. I'm just confused that when I do C-h v
> gnus-group-mode-map, it shows a lot of keybinds, but not these ones.
> I'm just curious why this is.
Maybe a better way to list those keys is `C-h b' in the group
buffer. Why those keys don't appear in `C-h v g-g-mode-map' is
that (probably) the keymap for the G-prefixed group keys are
explicitly defined as `gnus-group-group-map' in gnus-group.el.
next prev parent reply other threads:[~2014-04-08 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 1:23 Ian Kelling
2014-04-08 1:47 ` Katsumi Yamaoka [this message]
2014-04-08 22:56 ` Ian Kelling
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=b4mob0c7fty.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).