From: Sebastian Urban <mrsebastianurban@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48504@debbugs.gnu.org
Subject: bug#48504: Improve style of C-h t description (Preface)
Date: Thu, 20 May 2021 08:21:01 +0200 [thread overview]
Message-ID: <2dbee0a0-4c4a-cad0-ae8a-91e8ba88cbde@gmail.com> (raw)
In-Reply-To: <83tumyq0mk.fsf@gnu.org>
>>> How about
>>>
>>> To run the tutorial, start Emacs and type @kbd{C-h t} (that is,
>>> press and hold Control, then type h, then release Control and type
>>> t).
>>
>> Why @kbd/@key (commands for indication) can't be used here for
>> "Control"/"h"/"t"?
>
> Because we didn't yet explain this notation, that comes later in the
> manual.
This is becoming a surprisingly confusing issue...
So, we can't present keys or other KBD input with @key/@kbd style,
because of the notation, that e.g. makes keys like Control use @key
style, which is introduced later? Until that section - "(emacs) User
Input" perhaps - we can only write "Control"/"h"/"t" just like an
ordinary text? BTW, isn't @kbd{C-h t}, in the same sentence, and
@kbd{h}, in the same file (EMACS.TEXI - L128), against this rule as
well?
What is to explain at all? The fact that - e.g. in PDF - @kbd/@key
change font from Roman to Typewriter. It helps to distinguish the
input keys/chars from the rest of the paragraph. In your example "h"
and "t" may look like leftovers from a partially removed words...
which is something I want to avoid.
next prev parent reply other threads:[~2021-05-20 6:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 19:05 bug#48504: Improve style of C-h t description (Preface) Sebastian Urban
2021-05-18 19:19 ` Eli Zaretskii
2021-05-18 20:35 ` Sebastian Urban
2021-05-19 2:24 ` Eli Zaretskii
2021-05-19 11:17 ` Sebastian Urban
2021-05-19 11:56 ` Eli Zaretskii
2021-05-19 13:44 ` Sebastian Urban
2021-05-19 14:06 ` Eli Zaretskii
2021-05-20 6:21 ` Sebastian Urban [this message]
2021-05-20 7:06 ` Eli Zaretskii
2021-05-20 13:42 ` Sebastian Urban
2021-09-29 12:07 ` Stefan Kangas
2021-09-29 12:18 ` Eli Zaretskii
2021-09-29 13:11 ` Stefan Kangas
2022-07-13 12:00 ` Lars Ingebrigtsen
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=2dbee0a0-4c4a-cad0-ae8a-91e8ba88cbde@gmail.com \
--to=mrsebastianurban@gmail.com \
--cc=48504@debbugs.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).