From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61183@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#61183: 29.0.60; Add describe-repeat-maps to the manual
Date: Tue, 31 Jan 2023 10:45:25 +0100 [thread overview]
Message-ID: <87pmavvxze.fsf@gmail.com> (raw)
In-Reply-To: <83y1pj3m4z.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 Jan 2023 20:36:28 +0200")
>>>>> On Mon, 30 Jan 2023 20:36:28 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Juri Linkov <juri@linkov.net>
>> Its output is easy to understand for anyone who uses this feature
>> and just wants to check what commands are already supported.
Eli> That's not the correct criterion for judging documentation, definitely
Eli> not when the manual is concerned. The manual should be clear enough
Eli> to explain the command's effect even to someone who reads about
Eli> repeated commands for the first time.
Eli> And even if you only consider experienced users, how can a user
Eli> understand that these commands support repeating? Which part(s) of
Eli> that buffer say that in terns that are clear enough? A naïve reader
Eli> of the buffer will just see a list of commands and their bindings,
Eli> preceded by a sentence whose intent is hard to understand without some
Eli> background in Emacs keymaps.
How about putting something like
If `repeat-mode' is enabled, these keymaps determine which single key
can be used to repeat a command invoked via a full key sequence.
in the buffer produced by `descripe-repeat-maps'?
Robert
--
next prev parent reply other threads:[~2023-01-31 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 17:19 bug#61183: 29.0.60; Add describe-repeat-maps to the manual Juri Linkov
2023-01-30 17:59 ` Eli Zaretskii
2023-01-30 18:10 ` Juri Linkov
2023-01-30 18:36 ` Eli Zaretskii
2023-01-31 9:45 ` Robert Pluim [this message]
2023-01-31 14:07 ` Eli Zaretskii
2023-02-01 18:06 ` Juri Linkov
2023-02-02 13:37 ` Eli Zaretskii
2023-02-01 18:06 ` Juri Linkov
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=87pmavvxze.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=61183@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
/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.