From: Drew Adams <drew.adams@oracle.com>
To: Josh <josh@foxtail.org>, Eli Zaretskii <eliz@gnu.org>
Cc: 17362@debbugs.gnu.org
Subject: bug#17362: 24.4.50; inconsistent key notation: `ESC' vs `<ESC>'
Date: Tue, 29 Apr 2014 16:00:10 -0700 (PDT) [thread overview]
Message-ID: <e3d5b901-0060-4427-bff2-b9701f50cea3@default> (raw)
In-Reply-To: <CANdFEAHRYLHqgSVNNgWQoDM-m506mFB_hWd0aBF2jucGrncC2A@mail.gmail.com>
> Sorry to be mentioning this after you committed your changes, but I
> wanted to comment about the impact of these changes on new users.
> Difficulty specifying key bindings correctly is fairly common among
> newer users, and I think that this difficulty is worsened by
> occurrences in the documentation of non-canonical (with respect to
> kbd arguments) key notation. There's an EmacsWiki page[0] about key
> binding notation that reads in part, "Use C-h k to find out how Emacs
> describes the key sequence, and copy & paste that into your kbd
> string." It would be good if the info manual used the same notation.
>
> http://www.emacswiki.org/cgi-bin/wiki?KeyBindingNotation
That's what the discussion here after Eli's fix has been about.
But this is not really the best place to discuss or propose it.
Why don't you file another bug for this?
I have brought it up before, in emacs-devel and perhaps in one or
more bug reports, but maybe there is another chance for such a
simplification.
Unfortunately, Eli opposes it so far, and he is no doubt the
person the most interested in working on the manual (and the most
familiar with it and with its build tools). But AFAIK that does
not necessarily mean that the question is closed forever.
next prev parent reply other threads:[~2014-04-29 23:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<47b1a857-a5d6-4e5a-b8f6-f96f9e201c89@default>
[not found] ` <<CAH8Pv0i8RqY8JpPEurRycUwRp_C1_UZ5NN5MXwW3uQ74kYeQDQ@mail.gmail.com>
[not found] ` <<83fvkxo4kc.fsf@gnu.org>
2014-04-28 15:39 ` bug#17362: 24.4.50; inconsistent key notation: `ESC' vs `<ESC>' Drew Adams
2014-04-28 16:15 ` Eli Zaretskii
[not found] ` <<b73bc016-5fd5-4af5-879c-18c14a989a14@default>
[not found] ` <<83fvkwmagn.fsf@gnu.org>
2014-04-29 15:40 ` Drew Adams
2014-04-29 16:19 ` Eli Zaretskii
[not found] ` <<4294927c-08b3-4c65-83e4-1582e8d0d859@default>
[not found] ` <<838uqom7lm.fsf@gnu.org>
2014-04-29 17:27 ` Drew Adams
2014-04-29 17:51 ` Eli Zaretskii
2014-04-29 21:55 ` Josh
2014-04-29 23:00 ` Drew Adams [this message]
2014-04-30 2:55 ` Eli Zaretskii
[not found] ` <<f2425601-bc55-4f33-ba22-5a2045fdf78a@default>
[not found] ` <<8361lsm3b6.fsf@gnu.org>
2014-04-29 18:12 ` Drew Adams
2014-04-29 18:34 ` Eli Zaretskii
[not found] <<d035db75-bf2f-4a7e-bca3-684f76f17742@default>
[not found] ` <<8338gwlz7v.fsf@gnu.org>
2014-04-29 19:38 ` Drew Adams
2014-04-30 2:51 ` Eli Zaretskii
[not found] <<c30f764a-5327-47f4-8bf6-ef6ad993518d@default>
[not found] ` <<834n1cm1bx.fsf@gnu.org>
2014-04-29 19:09 ` Drew Adams
2014-04-29 19:20 ` Eli Zaretskii
2014-04-29 19:24 ` Eli Zaretskii
[not found] <<e9c40932-a5e6-4e19-ac69-5b656438a555@default>
[not found] ` <<83bnvlo2fh.fsf@gnu.org>
2014-04-28 16:20 ` Drew Adams
2014-04-28 14:29 Drew Adams
2014-04-28 14:49 ` Dani Moncayo
2014-04-28 15:25 ` Drew Adams
2014-04-29 15:17 ` Eli Zaretskii
2014-04-28 15:29 ` Eli Zaretskii
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=e3d5b901-0060-4427-bff2-b9701f50cea3@default \
--to=drew.adams@oracle.com \
--cc=17362@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=josh@foxtail.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).