all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Dani Moncayo <dmoncayo@gmail.com>
Cc: 17362@debbugs.gnu.org
Subject: bug#17362: 24.4.50; inconsistent key notation: `ESC' vs `<ESC>'
Date: Mon, 28 Apr 2014 08:39:06 -0700 (PDT)	[thread overview]
Message-ID: <e9c40932-a5e6-4e19-ac69-5b656438a555@default> (raw)
In-Reply-To: <<83fvkxo4kc.fsf@gnu.org>>

> > > Emacs manual: contrast node `Menu Bar' with node `Quitting'.  The former
> > > writes `ESC ESC ESC'; the latter writes `<ESC> <ESC> <ESC>'.
> > >
> > > IMO, the former is preferable.  (Note that (kbd "ESC") and (kbd "<ESC>")
> > > both act the same, however.)
> >
> > I'd also prefer "ESC" over "<ESC>" but then other strings like
> > "<TAB>", "<SPC>", "<RET>" or "<DEL>" should also be changed
> > accordingly.
> 
> Actually, the distinction should be between "ESC" (or "TAB" or "SPC")
> the key vs "ESC ESC ESC" the key sequence typed from the keyboard.  So
> not every <FOO> should suddenly become "FOO", it's a judgment call.

A difference in syntax for keyboard keys vs key sequences should not be
subject to judgment calls.  There are presumably clear-cut rules defining
the two different syntaxes.

I suppose that a particular sentence might be ambiguous as to which is
meant, but in that case perhaps the sentence needs rewording to make clear
which is meant.  In such a case, the meaning that users take from the text
(keyboard key vs key sequence) should not depend only on the syntax used.
Preferably the rest of the sentence would make clear which meaning is intended.

Anyway, feel free to make any judgments you feel appropriate wrt this
particular bug and the various occurrences in the manual (and the other
Emacs manuals).  And if you judge that there is no inconsistency
anywhere then feel free to close it.





       reply	other threads:[~2014-04-28 15:39 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     ` Drew Adams [this message]
2014-04-28 16:15       ` bug#17362: 24.4.50; inconsistent key notation: `ESC' vs `<ESC>' 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
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=e9c40932-a5e6-4e19-ac69-5b656438a555@default \
    --to=drew.adams@oracle.com \
    --cc=17362@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    --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.