From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: xah lee <xah@xahlee.org>,
1111@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#1111: describe-key's key notation display inconsistency
Date: Thu, 8 Aug 2019 17:14:44 -0700 (PDT) [thread overview]
Message-ID: <76f8d8ae-83ef-4062-881d-8e60a2a148a6@default> (raw)
In-Reply-To: <87sgqbqmv8.fsf@gmail.com>
> > The value of the event is a symbol.
>
> I don't understand where you're getting that idea from.
> (info "(elisp) Keyboard Events"):
>
> There are two kinds of input you can get from the keyboard:
> ordinary keys, and function keys. Ordinary keys correspond to
> (possibly modified) characters; the events they generate are
> represented in Lisp as characters.
We're not talking about ordinary keys. We're
talking about function keys. They're not
represented as characters. They're represented
as Lisp symbols.
(elisp) `Function Keys':
Function keys are represented in Emacs Lisp as
symbols; the symbol's name is the function key's
label, in lower case.
For example, pressing a key labeled <F1> generates
an input event represented by the symbol 'f1'.
(Note: not the symbol `<f1>' - see my statement that
I think the doc that says that the angle brackets
are part of the event name is incorrect, per this
doc passage.)
The event type of a function key event is the event
symbol itself. See Classifying Events.
... the symbol for the key <F3> with <META> held
down is `M-f3'.
Similarly, in (elisp) `Classifying Events' it talks
about event types also being symbols:
... the event type for a function key symbol is
the symbol itself.
"Function key symbol", there seems to be the
symbol talked about in `Function Keys'. So function
keys and their events and the event types are all
"represented in Emacs Lisp by symbols". Likewise,
event modifiers are symbols.
next prev parent reply other threads:[~2019-08-09 0:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 15:12 bug#1111: describe-key's key notation display inconsistency xah lee
2019-08-08 12:35 ` Stefan Kangas
2019-08-08 15:47 ` Drew Adams
2019-08-08 16:03 ` Noam Postavsky
2019-08-08 17:25 ` Drew Adams
2019-08-08 18:06 ` Noam Postavsky
2019-08-08 22:15 ` Drew Adams
2019-08-08 23:05 ` Noam Postavsky
2019-08-09 0:14 ` Drew Adams [this message]
2019-08-09 6:38 ` Eli Zaretskii
2021-09-24 22:00 ` Stefan Kangas
2021-09-24 22:49 ` bug#1111: [External] : " Drew Adams
2021-09-26 5:07 ` Xah Lee
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=76f8d8ae-83ef-4062-881d-8e60a2a148a6@default \
--to=drew.adams@oracle.com \
--cc=1111@debbugs.gnu.org \
--cc=npostavs@gmail.com \
--cc=stefan@marxist.se \
--cc=xah@xahlee.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).