From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Built-In Keybindingr associated with functions keys F2, F3, etc
Date: Sat, 24 Oct 2020 11:17:39 +0300 [thread overview]
Message-ID: <83y2jwghr0.fsf@gnu.org> (raw)
In-Reply-To: <54bdb735-681a-4429-b6f8-0ab9f1c366b0@default> (message from Drew Adams on Fri, 23 Oct 2020 15:49:41 -0700 (PDT))
> Date: Fri, 23 Oct 2020 15:49:41 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
>
> > You can usually get that information for any prefix key by typing
> > `<prefix> C-h'. So for example `<f2> C-h' shows:...
>
> (But <f1>, <f3>, <f4>, <f10>, <f11> are not, by default,
> prefix keys.)
Why does that matter, for the issue at hand? This is a kind of rigor
that should have no place in this discussion. Tassilo is factually
correct: the way he pointed out _is_ the way of asking Emacs about key
sequences that start with a given key.
> <f1> is bound to `help-command', which is a prefix command, and
> `C-h f help-command' tells you its definition is a keymap. But
> `<f1> C-h' doesn't tell you about keys with prefix <f1>.
It does here.
> The others I listed are bound to simple commands. They're not
> prefix keys. `C-h k' tells you about each one.
Yes. So either C-h k or <KEY> C-h will do.
next prev parent reply other threads:[~2020-10-24 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 19:42 Built-In Keybindingr associated with functions keys F2, F3, etc Christopher Dimech
2020-10-23 22:13 ` Tassilo Horn
2020-10-23 22:49 ` Drew Adams
2020-10-24 8:17 ` Eli Zaretskii [this message]
[not found] <<trinity-92d3fa12-3682-47fd-9f07-718fb0aecdad-1603482123573@3c-app-mailcom-bs08>
[not found] ` <<877drga8wf.fsf@gnu.org>
[not found] ` <<54bdb735-681a-4429-b6f8-0ab9f1c366b0@default>
[not found] ` <<83y2jwghr0.fsf@gnu.org>
2020-10-24 16:49 ` Drew Adams
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=83y2jwghr0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).