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 15:15:46 -0700 (PDT) [thread overview]
Message-ID: <bc6f255c-d501-481c-bd55-2031dc95501a@default> (raw)
In-Reply-To: <85k1bn3527.fsf@gmail.com>
> > Presumably the key described as `<M-D>' (or
> > `M-<D>', per Xah), where `<D>' is a function
> > key, would correspond to event `M-d', which
> > might already be problematic (no?).
>
> I don't think so, (kbd "M-d") => [?\M-d],
> but (kbd "<M-D>") => [M-D].
I'm talking about the _event_. The value
of the event is a symbol. In both cases
(I think) it would be the symbol `M-d'.
> > but have you ever come across a single-char
> > function-key name?
>
> No (and I didn't mean to say that assuming
> all function key names are multi-character
> is unreasonable).
(I didn't expect that you did mean that.)
My point (in this tangent discussion) is that
it is possible to drop the angle brackets.
And the result would be a lot less noise.
But unless we also added a convention such as
no single-char function-key names, there could
be some rare ambiguity.
One way to avoid that rare case of ambiguity
would be to use angle brackets only for the
case of single-char names.
next prev parent reply other threads:[~2019-08-08 22:15 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 [this message]
2019-08-08 23:05 ` Noam Postavsky
2019-08-09 0:14 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bc6f255c-d501-481c-bd55-2031dc95501a@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.