From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 17362@debbugs.gnu.org
Subject: bug#17362: 24.4.50; inconsistent key notation: `ESC' vs `<ESC>'
Date: Tue, 29 Apr 2014 11:12:22 -0700 (PDT) [thread overview]
Message-ID: <c30f764a-5327-47f4-8bf6-ef6ad993518d@default> (raw)
In-Reply-To: <<8361lsm3b6.fsf@gnu.org>>
> I'm not talking about help, I'm only talking about the manual. The
> bug report was about inconsistencies in the manual. At least that's
> how I perceived it, and that's the only issue I set out to fix.
Yes, thank you for that.
> > > > Seems like that would be a big change from the past and a change
> > > > from how Emacs itself communicates with users. AFAIK, Emacs
> > > > writes <delete> for the Delete key etc. The rule for function
> > > > keys and pseudo function keys has always been to use lowercase
> > > > (in angle brackets), no?
> > >
> > > Yes, because they are symbols. I did nothing about symbols, of
> > > course.
> >
> > What does that mean?
>
> Which part is unclear?
Apparently you agree that the rule for function keys is lowercase.
Yet you leave some of them capitalized or uppercase? And the reason
is because those that you make lowercase are symbols?
> > Emacs writes <backspace>. Why write <BACKSPACE>? Emacs writes
> > <delete>. Why write Delete or <Delete>?
>
> See the guidelines I used to decide on names and capitalization, I
> tried to explain why I choose this or that convention.
The convention used should be the one that Emacs itself uses to
write key sequences.
(And yes, this discussion is outside this bug report. I did not
ask in the report that you fix all key-sequence inconsistencies in
the manual. But that's what the current discussion is about.
That and the inconsistencies between the notations in the manual
and the notation in the Emacs UI.
> > My point is that the manual should write key sequences the same way
> > Emacs writes them interactively, e.g., in help output. It does not
> > refer to a <BACKSPACE> key or a Backspace key or a <CNTL>, <Control>,
> > Control, or Ctrl key. Emacs help writes <backspace> and C- in key
> > sequences.
>
> If that's the issue, then (a) it was nowhere clear from your original
> bug report, and (b) I will have nothing to do with it, sorry. I don't
> care enough about it to work on that.
1. Yes, it is outside this bug report.
2. Too bad you are not interested in it, but so be it.
> I only fixed inconsistencies in the manual, without any relation to
> what Emacs says in help mode.
You fixed only some inconsistencies in the manual, but that is OK
for this bug report. It is inconsistent to use <BACKSPACE> sometimes
and <Backspace> other times, <DELETE> and <Delete>, <left> and <Home>,
and so on.
But yes, beyond inconsistencies within the manual, the larger issue is
to get the manual in sync with the rest of Emacs, so there it uses the
same, single, key-sequence notation. And yes, that is outside this
bug report.
I am OK with (what I guess is) what you have fixed for this bug report.
> > Do you even agree that key sequences should be written the same way
> > in the manual as in the rest of Emacs? Do agree that the manual,
> > like the rest of Emacs, should write <C-left> and not C-<left>,
> > <C-home> and not C-<Home>?
>
> Perhaps it could be nice (although it never bothered me), but I think
> it's close to impossible now, due to various historical reasons. In
> any case, I'm not going to do anything about this, someone else will
> have to step forward. I found your complaint about inconsistencies in
> the manual justified, and I fixed that; my job here is now done.
Thank you for that.
next prev parent reply other threads:[~2014-04-29 18:12 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c30f764a-5327-47f4-8bf6-ef6ad993518d@default \
--to=drew.adams@oracle.com \
--cc=17362@debbugs.gnu.org \
--cc=eliz@gnu.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.