From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Describe keymap
Date: Mon, 14 Dec 2020 00:18:50 +0100 [thread overview]
Message-ID: <87wnxlxpk5.fsf@zoho.eu> (raw)
In-Reply-To: 874kkpzcoa.fsf@zoho.eu
Drew Adams wrote:
>> S <t> gnus-article-read-summary-send-keys
>>
>> the angle brackets;
>
> That's just the standard Emacs way of writing a key binding.
> `C-h k' and `C-h b' use the same syntax. `describe-keymap' does
> nothing special here.
Well, it might be the standard somewhere else, but here it is
the one exception:
[...]
S W gnus-article-wide-reply-with-original
S <t> gnus-article-read-summary-send-keys
C-h b gnus-article-describe-bindings
C-h c gnus-article-describe-key-briefly
C-h k gnus-article-describe-key
C-c C-b gnus-bug
C-c C-f gnus-summary-mail-forward
C-c TAB gnus-info-find-node
C-c RET gnus-article-mail
C-c ^ gnus-article-refer-article
[...]
>> <remap> Prefix Command
>> <remap> <self-insert-command> gnus-article-read-summary-keys
>>
>> ?
>
> Sorry, I don't understand the question. But see above.
> There's nothing special/different about how `describe-keymap'
> lists key bindings. It just shows the key bindings of
> a keymap in human-readable form (as opposed to what `C-h v'
> shows you for a keymap variable).
What do these lines mean?
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
next prev parent reply other threads:[~2020-12-13 23:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201213195427.jyn4vwkayqujbnwh.ref@Ergus>
2020-12-13 19:54 ` Describe keymap Ergus
2020-12-13 20:01 ` Drew Adams
2020-12-13 20:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-13 23:18 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2020-12-14 1:31 ` FW: " Drew Adams
2020-12-14 2:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 8:46 ` Robert Pluim
2020-12-14 9:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 9:57 ` Robert Pluim
2020-12-14 10:05 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-12-14 10:30 ` Robert Pluim
2020-12-14 13:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 17:08 ` Robert Pluim
2020-12-14 18:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-15 10:18 ` Robert Pluim
2020-12-15 20:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 13:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 1:31 ` Drew Adams
2020-12-14 2:33 ` Michael Heerdegen
2020-12-14 2:40 ` Emanuel Berg via Users list for the GNU Emacs text editor
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnxlxpk5.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).