From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: "49265@debbugs.gnu.org" <49265@debbugs.gnu.org>,
Robert Pluim <rpluim@gmail.com>, Ergus <spacibba@aol.com>
Subject: bug#49265: [External] : bug#49265: 28.0.50; repeat mode feature request
Date: Tue, 6 Jul 2021 18:25:51 +0000 [thread overview]
Message-ID: <SA2PR10MB4474818194B18EA1B75A7202F31B9@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <878s2jcoqp.fsf@mail.linkov.net>
> >> Maybe Drew could suggest a better text?
> >
> > My suggestion would be to not say anything about the
> > keymaps involved. What's the purpose in trying to do
> > that? What additional help do you mean to provide
> > by it?
>
> But the keymaps are the essential part of this feature.
Sorry, I haven't understood that. How so?
What does the doc/help tell us about their
importance for "this feature"?
> >> I propose to rename this command to `describe-repeat-mode'.
> >
> > That sounds like it's a command that describes some
> > mode called `repeat-mode'.
>
> This is correct, the mode is called `repeat-mode'.
I see. I don't see that in Emacs releases.
Presumably it is new for Emacs 28. So does
this command describe the mode? Or does it
just list key bindings (as `describe-keymap'
does)?
> > I don't have a great suggestion for the name. IIUC,
> > the command lists bindings of commands that are
> > defined using function `repeat'.
> >
> > Maybe `list-repeat-commands', as OP suggested. Or
> > maybe `describe-repeat-bindings', as it is bindings
> > that are listed/described. I don't think it's
> > about describing the commands - their bindings are
> > listed.
>
> Thanks for the suggestion, this helped to rename it
> to the most proper name `describe-repeat-maps',
> because this feature is based on `repeat-map' props.
> Also did my best to fix text strings.
So are there multiple repeat maps? And what
about what you hinted above - that this command
describes `repeat-mode'? Is there perhaps a
`repeat-mode-map', and is this about that?
Not clear to me (not that that matters).
next prev parent reply other threads:[~2021-07-06 18:25 UTC|newest]
Thread overview: 44+ 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
2021-07-06 1:31 ` Drew Adams
2021-07-06 17:54 ` Juri Linkov
2021-07-06 18:25 ` Drew Adams [this message]
2021-06-30 19:55 ` Juri Linkov
[not found] ` <87r1cdz72i.fsf@gmail.com>
[not found] ` <875ytn8ufp.fsf@mail.linkov.net>
2021-10-24 14:20 ` Robert Pluim
2021-10-24 19:12 ` Juri Linkov
2021-10-24 20:02 ` Robert Pluim
2021-10-25 7:41 ` Juri Linkov
2021-10-25 8:55 ` Robert Pluim
2021-10-25 9:21 ` Stefan Kangas
2021-10-25 9:59 ` Robert Pluim
2021-10-25 10:14 ` Andreas Schwab
2021-10-25 17:54 ` Juri Linkov
2021-10-25 18:08 ` Stefan Monnier
2021-10-25 19:59 ` Robert Pluim
2021-10-25 20:57 ` Stefan Monnier
2021-10-26 10:06 ` Robert Pluim
2021-10-26 10:25 ` Robert Pluim
2021-10-26 12:39 ` Stefan Monnier
2021-10-26 12:46 ` Robert Pluim
2021-10-25 17:58 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SA2PR10MB4474818194B18EA1B75A7202F31B9@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 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.