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: Thu, 8 Aug 2019 14:35:23 +0200	[thread overview]
Message-ID: <CADwFkm=KKxsEZ40GJHDOP1_u8eaQih-DsSLYXrapaZb-YCgZLw@mail.gmail.com> (raw)
In-Reply-To: <06D80DE1-FCD6-45BB-B2D9-A968F797971C@xahlee.org>

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>?

Would anyone else want to weigh in on this old wishlist item?  Is this a
good idea, even if it is very minor, or should we close this as wontfix?

FWIW, I personally don't mind either way.

Thanks,
Stefan Kangas





  reply	other threads:[~2019-08-08 12:35 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 [this message]
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   ` 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='CADwFkm=KKxsEZ40GJHDOP1_u8eaQih-DsSLYXrapaZb-YCgZLw@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).