unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stephen Berman'" <stephen.berman@gmx.net>,
	"'Eli Zaretskii'" <eliz@gnu.org>
Cc: 13219@debbugs.gnu.org, cyd@gnu.org
Subject: bug#13219: 24.3.50; missing `...' in Emacs manual
Date: Fri, 21 Dec 2012 09:31:57 -0800	[thread overview]
Message-ID: <E9506440754D4C12A54479CCE4DD3F1C@us.oracle.com> (raw)
In-Reply-To: <87bodn8h6r.fsf@rosalinde.fritz.box>

> Actually, the convention appears to be: enclose single keys 
> labels that are not single characters in angle brackets but
> quote single keys labels that are single characters (as well
> as labels of key sequences);

Yes, and that inconsistency is unnecessary.

My guess is that this double-standard convention was implemented/adopted due to
a misunderstanding of what " " means in key-sequence notation.

" " separates keys of the sequence, nothing more.  It never denotes the space
key, which `SPC' denotes in key sequence notation.

`f 1' means the key sequence of hitting the `f' key followed by hitting the `1'
key.

`f1' means the single-key key sequence of hitting the `f1' key (a function key).

`f SPC 1' means the key sequence of hitting `f' then `SPC then `1'.

There is no good reason to have introduced two kinds of quoting (angle brackets
and `...').  That is, there is no necessity for that.

Function keys and keys such as `ESC' `DEL' are unambiguously denoted using only
`...' syntax.  And it is not too late to get rid of the kludge - or at least
make it optional for those who are hooked on it.






      reply	other threads:[~2012-12-21 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18 14:27 bug#13219: 24.3.50; missing `...' in Emacs manual Drew Adams
2012-12-21  8:08 ` Chong Yidong
2012-12-21  8:24   ` Drew Adams
2012-12-21  9:22     ` Eli Zaretskii
2012-12-21 16:49       ` Drew Adams
2012-12-21 17:10       ` Stephen Berman
2012-12-21 17:31         ` Drew Adams [this message]

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=E9506440754D4C12A54479CCE4DD3F1C@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=13219@debbugs.gnu.org \
    --cc=cyd@gnu.org \
    --cc=eliz@gnu.org \
    --cc=stephen.berman@gmx.net \
    /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).