unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>, xah lee <xah@xahlee.org>
Cc: "1111@debbugs.gnu.org" <1111@debbugs.gnu.org>
Subject: bug#1111: [External] : bug#1111: describe-key's key notation display inconsistency
Date: Fri, 24 Sep 2021 22:49:27 +0000	[thread overview]
Message-ID: <SJ0PR10MB548801DF2D11856CD187823BF3A49@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CADwFkmkdOKk7YegsJCGMC+0m44iNZfj0RheKCEhAmonQNwuNng@mail.gmail.com>

> This is now the case in Emacs 28, from NEWS:
> 
>     ** Modifiers now go outside angle brackets in pretty-printed key
>     bindings.
>     For example, 'RET' with Control and Meta modifiers is now shown as
>     'C-M-<return>' instead of '<C-M-return>'.  Either variant can be
>     used
>     as input; functions such as 'kbd' and 'read-kbd-macro' accept both
>     styles as equivalent (they have done so for a long time).

Unfortunate.

Should have instead made the manuals consistent
with the way Emacs has (forever) talked about
itself, if consistency was the aim.  (Internal
/ local consistency is always more important
than global consistency.

This will require at least some 3rd-party docs
(HTML, wiki, plain-text, whatever) to change,
where such bindings are explicit (not via
\\[...]).

And as I mentioned in this thread, it will
lead users to misread and confuse things like
`C-x <right>' with `C-<right>'.  There's
no such problem with `<C-right>'.
___

Beyond that, if the change is what was requested
by the OP, then it's a change in *Help* (perhaps
among other things).  And yet that's not even
mentioned in the NEWS.

What does "in pretty-printed key bindings" refer
to?  Users will rightfully wonder.  The manuals?
(No, they already used C-<right>.)  Output of
`pp' commands?  Messages?  Byte-compiler
warnings?  All of the above?  None of the above?

  reply	other threads:[~2021-09-24 22:49 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
2019-08-09  6:38                 ` Eli Zaretskii
2021-09-24 22:00 ` Stefan Kangas
2021-09-24 22:49   ` Drew Adams [this message]
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=SJ0PR10MB548801DF2D11856CD187823BF3A49@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=1111@debbugs.gnu.org \
    --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).