From: Stephen Berman <stephen.berman@gmx.net>
To: 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 18:10:20 +0100 [thread overview]
Message-ID: <87bodn8h6r.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <83fw2zn4if.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 21 Dec 2012 11:22:48 +0200")
On Fri, 21 Dec 2012 11:22:48 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: "Drew Adams" <drew.adams@oracle.com>
>> Date: Fri, 21 Dec 2012 00:24:21 -0800
>> Cc: 13219@debbugs.gnu.org
>>
>> > It is the convention in the manual not to insert `..' around single
>> > function keys which are already printed like <this>. Not a
>> > bug (and no bike-shedding please).
>>
>> See attached screenshot. Are you perhaps trying to make a virtue (and a
>> convention) out of mistake? Do you honestly think it is more readable to have
>> these exceptions?
>
> Are you referring to the highlight? If so, who or what did the
> highlighting of `..' strings in that screenshot? I don't see such
> highlighting in "emacs -Q".
>
> We had this argument before. <FOO> is a name of a single key. We
> don't quote single keys named by their labels, only key sequences.
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);
cf. (emacs) Dired Navigation:
"For extra convenience, <SPC> and `n' in Dired are equivalent to `C-n'."
Steve Berman
next prev parent reply other threads:[~2012-12-21 17:10 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 [this message]
2012-12-21 17:31 ` Drew Adams
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=87bodn8h6r.fsf@rosalinde.fritz.box \
--to=stephen.berman@gmx.net \
--cc=13219@debbugs.gnu.org \
--cc=cyd@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 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).