[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#3516: 23.0.94; function key names in Info
From: |
Drew Adams |
Subject: |
bug#3516: 23.0.94; function key names in Info |
Date: |
Tue, 12 Jul 2011 09:38:24 -0700 |
> "@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>'?
- bug#3516: 23.0.94; function key names in Info, Lars Magne Ingebrigtsen, 2011/07/12
- bug#3516: 23.0.94; function key names in Info, Eli Zaretskii, 2011/07/12
- bug#3516: 23.0.94; function key names in Info,
Drew Adams <=
- bug#3516: 23.0.94; function key names in Info, Eli Zaretskii, 2011/07/12
- bug#3516: 23.0.94; function key names in Info, Drew Adams, 2011/07/12
- bug#3516: 23.0.94; function key names in Info, Eli Zaretskii, 2011/07/12
- bug#3516: 23.0.94; function key names in Info, Drew Adams, 2011/07/12
- bug#3516: 23.0.94; function key names in Info, Eli Zaretskii, 2011/07/12