From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>,
"'Lars Magne Ingebrigtsen'" <larsi@gnus.org>
Cc: 3516@debbugs.gnu.org
Subject: bug#3516: 23.0.94; function key names in Info
Date: Tue, 12 Jul 2011 09:38:24 -0700 [thread overview]
Message-ID: <E4EC0BEE2B2E441187A216F08002ACF3@us.oracle.com> (raw)
In-Reply-To: <838vs3fq0t.fsf@gnu.org>
> "@key{F1}" in Texinfo produces "<F1>" in Info,
> without the single quotes. In the printed output it produces
> something resembling a keyboard key with a label on it. Taking these
> in quotes would be wrong, e.g. because then "@kbd{C-x @key{RET}}"
> would produce `C-x `<RET>'' with nested quotes which looks ugly.
What you describe is an implementation problem (Texinfo, Info).
What I describe is from a user point of view: the resulting appearance in the
Info manual.
No one is suggesting that `C-x `<RET>'' should be used.
The point is that `<RET>' should be used.
The entire key sequence - whatever that key sequence is, should be in quotes,
consistently, to indicate a key sequence. `C-x <RET>' and `<RET>' both
correspond to the same convention: put the sequence of keys in quotes.
We don't write just i - we write `i' when we want to refer to the key sequence
consisting of just the i key. And we write `C-x i' when we want to refer to the
sequence of the C-x key followed by the i key.
And we write `C-x <RET>' to refer to the sequence of the C-x key followed by the
<RET> key. Why should we write <RET> for the key sequence `<RET>'?
next prev parent reply other threads:[~2011-07-12 16:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 16:11 bug#3516: 23.0.94; function key names in Info Drew Adams
2009-06-10 22:23 ` Eli Zaretskii
2009-06-10 22:33 ` Drew Adams
2009-06-11 10:42 ` Eli Zaretskii
2009-06-11 15:33 ` Drew Adams
2011-07-12 12:47 ` Lars Magne Ingebrigtsen
2011-07-12 16:00 ` Eli Zaretskii
2011-07-12 16:38 ` Drew Adams [this message]
2011-07-12 17:15 ` Eli Zaretskii
2011-07-12 20:04 ` Drew Adams
2011-07-12 20:30 ` Eli Zaretskii
2011-07-12 21:03 ` Drew Adams
2011-07-13 3:00 ` 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=E4EC0BEE2B2E441187A216F08002ACF3@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=3516@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.