From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: rpluim@gmail.com, 61183-done@debbugs.gnu.org
Subject: bug#61183: 29.0.60; Add describe-repeat-maps to the manual
Date: Thu, 02 Feb 2023 15:37:42 +0200 [thread overview]
Message-ID: <83a61wxk61.fsf@gnu.org> (raw)
In-Reply-To: <86wn516z0z.fsf@mail.linkov.net> (message from Juri Linkov on Wed, 01 Feb 2023 20:06:36 +0200)
> From: Juri Linkov <juri@linkov.net>
> Cc: Robert Pluim <rpluim@gmail.com>, 61183@debbugs.gnu.org
> Date: Wed, 01 Feb 2023 20:06:36 +0200
>
> >> 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'?
> >
> > This text is much better, thanks.
>
> Now added to the docstring.
>
> > However, it only talks about the
> > keymaps, whereas the window we pop shows also some key bindings for
> > each keymap. The explanatory text should say something about that as
> > well, I think. Such an explanation would probably clarify why the
> > text says "single" in "single key", which currently looks "out of the
> > blue".
Thanks, I've made some further improvements in this and related
documentation.
I think we can now close this bug.
next prev parent reply other threads:[~2023-02-02 13:37 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
2023-01-31 14:07 ` Eli Zaretskii
2023-02-01 18:06 ` Juri Linkov
2023-02-02 13:37 ` Eli Zaretskii [this message]
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=83a61wxk61.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61183-done@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=rpluim@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.