From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Sebastian Urban <mrsebastianurban@gmail.com>, 48504@debbugs.gnu.org
Subject: bug#48504: Improve style of C-h t description (Preface)
Date: Wed, 29 Sep 2021 05:07:09 -0700 [thread overview]
Message-ID: <CADwFkmkDaxxeG5LnDda-=+G+yRVxzvmzA3YO5xtchJxmw9tarw@mail.gmail.com> (raw)
In-Reply-To: <837djvq6n2.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 19 May 2021 14:56:17 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> No, I mean to change this:
>> (which is ``control h and then t'')
>> into this:
>> (hold down @key{Control} and type @kbd{h}, then let go of
>> @key{Control} and type @kbd{t})
>
> That's awkward. 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).
All users already know the notation Ctrl+X if they have ever used a
computer. We can safely assume this most basic level of computer
literacy.
So this is better written as:
> To run the tutorial, start Emacs and type @kbd{C-h t} (that is,
> @kbd{Ctrl+H}, then @kbd{T}).
(There is no confusion here with regards to @kbd{T} and @kbd{t}, because
everywhere else our "T" is written as "Shift+T".)
next prev parent reply other threads:[~2021-09-29 12:07 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
2021-05-20 7:06 ` Eli Zaretskii
2021-05-20 13:42 ` Sebastian Urban
2021-09-29 12:07 ` Stefan Kangas [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmkDaxxeG5LnDda-=+G+yRVxzvmzA3YO5xtchJxmw9tarw@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=48504@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mrsebastianurban@gmail.com \
/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.