From: Eli Zaretskii <eliz@gnu.org>
To: 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 19:00:02 +0300 [thread overview]
Message-ID: <838vs3fq0t.fsf@gnu.org> (raw)
In-Reply-To: <m3oc0zr7hu.fsf@quimbies.gnus.org>
> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Date: Tue, 12 Jul 2011 14:47:09 +0200
> Cc: 3516@debbugs.gnu.org
>
> "Drew Adams" <drew.adams@oracle.com> writes:
>
> > We see things like <F1>, <F2>, <RET>, and <ESC> without single
> > quotes. Similarly, in other parts of the manual.
> >
> > Shouldn't those be `<f1>', `<f2>', `<RET>', and `<ESC>'?
>
> That might be argued, but the difference you're seeing is the difference
> between these two markups:
>
> @kbd{C-h}
> @key{F1}
Yes, that's true. "@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.
next prev parent reply other threads:[~2011-07-12 16:00 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 [this message]
2011-07-12 16:38 ` Drew Adams
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
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=838vs3fq0t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=3516@debbugs.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 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).