From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 61183@debbugs.gnu.org
Subject: bug#61183: 29.0.60; Add describe-repeat-maps to the manual
Date: Mon, 30 Jan 2023 19:59:44 +0200 [thread overview]
Message-ID: <838rhj52en.fsf@gnu.org> (raw)
In-Reply-To: <86pmawgl17.fsf@mail.linkov.net> (message from Juri Linkov on Mon, 30 Jan 2023 19:19:56 +0200)
> From: Juri Linkov <juri@linkov.net>
> Date: Mon, 30 Jan 2023 19:19:56 +0200
>
> This patch adds describe-repeat-maps to the Info manual:
Thanks.
> +navigate @code{next-error} matches, @kbd{C-x ] ] [ [} to navigate
> +through pages, and other listed in @code{describe-repeat-maps}.
"and other commands", I presume?
Also, saying that commands are "listed in" a function sounds
awkwardly; I guess you meant in the window shown by
describe-repeat-maps instead?
And finally, I think this is insufficient to document
describe-repeat-maps, because its output is not very
self-explanatory. I actually have difficulty understanding what it
wants to tell me. The heading line says
A list of keymaps used by commands with the symbol property `repeat-map'
which isn't a user-level information. This is followed by keymap
names and some bindings in each keymap. What is the user supposed to
understand from that? I think we lack some short introductory text
immediately after the heading. Or maybe the manual should have some
more detailed explanation of what that command shows.
next prev parent reply other threads:[~2023-01-30 17:59 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 [this message]
2023-01-30 18:10 ` Juri Linkov
2023-01-30 18:36 ` Eli Zaretskii
2023-01-31 9:45 ` Robert Pluim
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=838rhj52en.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61183@debbugs.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.