From: Drew Adams <drew.adams@oracle.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: "49265@debbugs.gnu.org" <49265@debbugs.gnu.org>,
Ergus <spacibba@aol.com>, Juri Linkov <juri@linkov.net>
Subject: bug#49265: [External] : bug#49265: 28.0.50; repeat mode feature request
Date: Mon, 5 Jul 2021 14:53:28 +0000 [thread overview]
Message-ID: <SA2PR10MB44747A5CEB724CC58DE5D714F31C9@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87bl7hccr7.fsf@gmail.com>
> Drew> The text is ambiguous. If that's what you mean,
> Drew> please reword it. For example, this unambiguously
> Drew> applies "repeatable" only to "commands":
>
> 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.
Yes, that's what I understood. So the proposed doc
misleads. (And it doesn't describe all such keymaps,
because it doesn't consider all repeatable commands -
see next.)
> I still think we should not mention keymaps at all, only bindings.
I agree.
And as I mentioned earlier, it should be made clear
in the doc that "repeatable" here means only commands
defined using `repeat.el'.
There are other ways to define repeatable commands,
and those commands aren't represented by this
describe feature.
(It's not even clear to me that this feature really
helps users. A naming convention (combined with
`commandp', of course) makes more sense to me.)
next prev parent reply other threads:[~2021-07-05 14:53 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 [this message]
2021-07-05 21:04 ` Juri Linkov
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=SA2PR10MB44747A5CEB724CC58DE5D714F31C9@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=49265@debbugs.gnu.org \
--cc=juri@linkov.net \
--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).