From: Drew Adams <drew.adams@oracle.com>
To: "Lars Ingebrigtsen" <larsi@gnus.org>,
"Mattias Engdegård" <mattiase@acm.org>
Cc: 45536@debbugs.gnu.org
Subject: bug#45536: [PATCH] Pretty-print keys without <> around modifiers
Date: Fri, 1 Jan 2021 11:41:21 -0800 (PST) [thread overview]
Message-ID: <3bda3811-f45e-40d1-ad66-1c02f72f729d@default> (raw)
In-Reply-To: <87h7o1c4uv.fsf@gnus.org>
> The only instance I could find of "M-<[a-z]" was this from the manual?
> (kbd "C-M-<down>") @result{} [C-M-down]
Which manual are we talking about? And are we
talking about Info or a printed manual?
With Info:
In the Elisp manual, I see `M-<end>' and an
occurrence of (kbd "C-M-<down>").
In the Emacs manual, I see `C-<Delete>',
`M-<PageUp>, `M-<PageDown>', `M-<prior>',
`M-<next>', `M-<kp-8>', ...
(OK, some of those also have an uppercase
letter or a numeral.)
prev parent reply other threads:[~2021-01-01 19:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 16:21 bug#45536: [PATCH] Pretty-print keys without <> around modifiers Mattias Engdegård
2020-12-29 18:31 ` Drew Adams
2020-12-29 19:50 ` Mattias Engdegård
2020-12-29 20:14 ` Drew Adams
2020-12-29 20:01 ` Eli Zaretskii
2020-12-29 22:27 ` Mattias Engdegård
2020-12-30 3:54 ` Lars Ingebrigtsen
2020-12-30 9:52 ` Mattias Engdegård
2020-12-31 4:35 ` Lars Ingebrigtsen
2020-12-31 9:59 ` Mattias Engdegård
2020-12-31 12:29 ` Mattias Engdegård
2021-01-01 10:46 ` Lars Ingebrigtsen
2021-01-01 11:51 ` Mattias Engdegård
2021-01-01 11:54 ` Lars Ingebrigtsen
2021-01-02 17:20 ` Mattias Engdegård
2021-01-02 18:25 ` Drew Adams
2021-01-05 10:52 ` Mattias Engdegård
2021-01-05 10:47 ` Mattias Engdegård
2021-05-17 15:11 ` Lars Ingebrigtsen
2021-01-01 12:00 ` Eli Zaretskii
2021-01-01 12:10 ` Mattias Engdegård
2021-01-01 12:28 ` Eli Zaretskii
2021-01-01 12:43 ` Mattias Engdegård
2021-01-01 12:54 ` Eli Zaretskii
2021-01-01 13:29 ` Mattias Engdegård
2021-01-01 13:34 ` Eli Zaretskii
2021-01-01 19:41 ` Drew Adams [this message]
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=3bda3811-f45e-40d1-ad66-1c02f72f729d@default \
--to=drew.adams@oracle.com \
--cc=45536@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.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.