unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: xah lee <xah@xahlee.org>
Cc: 1111@debbugs.gnu.org
Subject: bug#1111: describe-key's key notation display inconsistency
Date: Fri, 24 Sep 2021 15:00:31 -0700	[thread overview]
Message-ID: <CADwFkmkdOKk7YegsJCGMC+0m44iNZfj0RheKCEhAmonQNwuNng@mail.gmail.com> (raw)
In-Reply-To: <06D80DE1-FCD6-45BB-B2D9-A968F797971C@xahlee.org> (xah lee's message of "Tue, 7 Oct 2008 08:12:48 -0700")

tags 1111 fixed
close 1111 28.1
thanks

xah lee <xah@xahlee.org> writes:

> When doing a describe-key on C-<backspace>, emacs prints <C-backspace>
> instead. Similar for any other special key whose macro notation are bracketed by
> angle brackets. e.g. <down>, <F6>, <return>, <kp-1>, etc. Where, emacs puts the
> entire thing inside angle brackets instead of the more traditional of modifier
> followed by dash followed by key name.
>
> Although these are identical as far as kbd function is concerned, but wouldn't
> it be more intuitively consistent by using C-<key> instead of <C-key>?

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).

I'm therefore closing this bug report.





  parent reply	other threads:[~2021-09-24 22:00 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 [this message]
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=CADwFkmkdOKk7YegsJCGMC+0m44iNZfj0RheKCEhAmonQNwuNng@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=1111@debbugs.gnu.org \
    --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).