From: Noam Postavsky <npostavs@gmail.com>
To: Drew Adams <drew.adams@oracle.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, 08 Aug 2019 12:03:42 -0400 [thread overview]
Message-ID: <85mugj3aqp.fsf@gmail.com> (raw)
In-Reply-To: <d5739584-8ac3-4fd5-be6e-7fb14899414c@default> (Drew Adams's message of "Thu, 8 Aug 2019 08:47:45 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> I've said before (not in this thread, most likely)
> that I think that the Emacs manuals should use the
> exact same notation that Emacs itself uses
> interactively.
>
> That means the manuals should use <C-return>, not
> C-<return>. But they don't.
Having Emacs print C-<return>, as suggested in the OP, would also solve
the consistency, yes? I think it's a bit more readable, so I would be
in favour of that.
> ---
>
> FWIW, I've also argued that we do not need
> angle-bracket notation at all. We can drop it and
> still be completely unambiguous and consistent.
That assumes all function key names are longer than one letter, right?
next prev parent reply other threads:[~2019-08-08 16:03 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 [this message]
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
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=85mugj3aqp.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=1111@debbugs.gnu.org \
--cc=drew.adams@oracle.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.