From: Juri Linkov <juri@linkov.net>
To: Robert Pluim <rpluim@gmail.com>
Cc: "49265@debbugs.gnu.org" <49265@debbugs.gnu.org>,
Ergus <spacibba@aol.com>
Subject: bug#49265: [External] : bug#49265: 28.0.50; repeat mode feature request
Date: Tue, 06 Jul 2021 00:04:07 +0300 [thread overview]
Message-ID: <877di41m40.fsf@mail.linkov.net> (raw)
In-Reply-To: <87bl7hccr7.fsf@gmail.com> (Robert Pluim's message of "Mon, 05 Jul 2021 11:48:28 +0200")
> Drew> Describe keymaps and repeatable commands.
>
> Drew> But is "describe keymaps" appropriate? Or are the
> Drew> keymaps that are described here only certain ones?
>
> It only describes keymaps that have bindings to repeatable commands in
> them. I still think we should not mention keymaps at all, only bindings.
I checked again, and it seems everything is already correct:
currently the Help buffer groups repeatable commands
by the keymap that is activated in post-command-hook.
Then keymap names have links to the Help buffer that
shows information about the keymap: all its keybindings, etc.
using `describe-keymap'.
Also every command has a link to the Help buffer
that describes that command.
Indeed, there is text "keymap is repeatable by these commands"
in the sense that the keymap is activated for repetition
in post-command-hook.
Maybe Drew could suggest a better text?
One thing I see that could be improved is a too ambiguous name `describe-repeat'.
I propose to rename this command to `describe-repeat-mode'.
next prev parent reply other threads:[~2021-07-05 21:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87czs53aei.fsf.ref@aol.com>
2021-06-28 22:13 ` bug#49265: 28.0.50; repeat mode feature request Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-29 8:38 ` Juri Linkov
2021-06-29 15:25 ` bug#49265: [External] : " Drew Adams
2021-06-29 20:37 ` Juri Linkov
2021-06-29 21:28 ` Drew Adams
2021-06-30 9:50 ` Robert Pluim
2021-06-30 15:10 ` Drew Adams
2021-06-29 20:36 ` Juri Linkov
2021-06-29 21:33 ` bug#49265: [External] : " Drew Adams
2021-06-30 9:59 ` Robert Pluim
2021-06-30 15:11 ` Drew Adams
2021-06-30 19:56 ` Juri Linkov
2021-06-30 21:15 ` Drew Adams
2021-07-04 20:31 ` Juri Linkov
2021-07-04 21:09 ` Drew Adams
2021-07-05 9:48 ` Robert Pluim
2021-07-05 14:53 ` Drew Adams
2021-07-05 21:04 ` Juri Linkov [this message]
2021-07-06 1:31 ` Drew Adams
2021-07-06 17:54 ` Juri Linkov
2021-07-06 18:25 ` Drew Adams
2021-06-30 19:55 ` Juri Linkov
2021-11-15 17:51 ` Juri Linkov
2021-11-15 18:21 ` Juri Linkov
2021-11-17 17:01 ` Juri Linkov
2021-11-18 10:16 ` Robert Pluim
2021-11-18 17:44 ` 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
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=877di41m40.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=49265@debbugs.gnu.org \
--cc=rpluim@gmail.com \
--cc=spacibba@aol.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 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).