From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: 36525@debbugs.gnu.org, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#36525: M-x default when cursor on top of a M-x command in INFO
Date: Mon, 8 Jul 2019 14:37:14 -0700 (PDT) [thread overview]
Message-ID: <8e584ef5-0d1b-4ed0-97e9-b22252289a7f@default> (raw)
In-Reply-To: <87bly4451d.fsf@mail.linkov.net>
> > I will point out that `M-.' is a repeatable
> > key. And a repeatable key is good for a
> > command that is repeatable, such as doing
> > something to/with consecutive bits of text
> > (e.g. "things") from a buffer.
>
> A keybinding doesn't need to be a single key
> to be repeatable. ‘C-x e e e’ is repeatable.
Agreed 100%. In general, I put most of my
repeatable keys on a prefix key.
I don't argue that a key sequence to grab
stuff from the buffer and insert it into the
minibuffer needs to be a single key.
I do think that a repeatable key sequence,
especially one that is a single key (such as
`M-.') should generally not be wasted on a
non-repeatable command (such as, presumably,
`xref-find-definitions').
Such a general rule (in my mind) can have
exceptions, of course, and there's no urgency to
try to rebind all such non-repeatable commands,
to liberate their keys for repeatable commands.
next prev parent reply other threads:[~2019-07-08 21:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 11:17 bug#36525: M-x default when cursor on top of a M-x command in INFO 積丹尼 Dan Jacobson
2019-07-06 15:55 ` Drew Adams
2019-07-07 0:25 ` 積丹尼 Dan Jacobson
2019-07-07 22:43 ` Juri Linkov
2019-07-08 0:27 ` Drew Adams
2019-07-08 20:58 ` Juri Linkov
2019-07-08 21:37 ` Drew Adams [this message]
2019-07-09 20:09 ` Juri Linkov
2019-07-09 21:07 ` Drew Adams
2019-07-07 13:55 ` Basil L. Contovounesios
2019-07-09 8:52 ` 積丹尼 Dan Jacobson
2019-07-09 10:55 ` Stefan Kangas
2019-07-09 11:10 ` 積丹尼 Dan Jacobson
2019-07-09 12:24 ` Stefan Kangas
2019-07-09 12:24 ` Basil L. Contovounesios
2019-07-15 8:43 ` Sebastian Urban
2019-07-09 12:24 ` Basil L. Contovounesios
2019-10-14 20:53 ` Lars Ingebrigtsen
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=8e584ef5-0d1b-4ed0-97e9-b22252289a7f@default \
--to=drew.adams@oracle.com \
--cc=36525@debbugs.gnu.org \
--cc=jidanni@jidanni.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 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).