all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Sun, 7 Jul 2019 17:27:44 -0700 (PDT)	[thread overview]
Message-ID: <18bc1649-6d5b-42c4-bb12-3630b0728b9c@default> (raw)
In-Reply-To: <87r2711n5i.fsf@mail.linkov.net>

> > A better way to handle this is to have a key
> > (Icicles uses `M-.') that pulls text from the
> > buffer into the minibuffer, appending it to
> > whatever input text might already be there.
> >
> > Summary:
> >
> > Repeated `M-.' can have two different behaviors.
> > You can choose (by an option) which one to use.
> > [...]
> >
> > Whether vanilla Emacs would allow flexibility
> > to this degree is not so important as at
> > least having Emacs have a key that grabs
> > _something_ from the buffer text and appends
> > it to minibuffer input.  Choice #2 above is
> > pretty simple to realize - give users an
> > option to specify which kind of text thing
> > they want to insert.
> 
> Do you think `M-.' is a suitable key for vanilla Emacs?
> Its global keybinding is `xref-find-definitions',
> but is this command useful in the minibuffer?
> Or could be taken for grabbing text from the buffer
> to the minibuffer?

Default key choice preferences are somewhat
of a mine field for discussion...

Dunno whether `xref-find-definitions' is
usable from the active minibuffer.  I'm
not familiar with it.  Perhaps so, with
non-nil `enable-recursive-minibuffers'.

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.

Is `xref-find-definitions' a repeatable
command (i.e. by holding the key pressed)?
On the other hand, in the old days `M-.'
was bound to `find-tag', which was not
repeatable (unless perhaps with non-nil
`enable-recursive-minibuffers').

In Icicle (minor) mode, where `M-.' is
bound to a command that inserts buffer
text into the minibuffer, I've never
noticed any conflict between that and
the global binding of `M-.'.  That may be
some evidence that it would be OK to use
it for something similar in the vanilla
Emacs minibuffer.

---

All of that said, I'd suggest that,
_other things being equal_, keys like
`M-.' should not be bound globally to
commands that can't benefit from holding
them down to repeat the action.

`M-.' was bound to `find-tag' eons ago,
before there were so many default key
bindings, so many modes, so many libraries,
and so many commands that are repeatable.

It's not as if repeatable key bindings
are as scarce as berkelium, but there's
also no great reason to "waste" them on
non-repeatable commands.  Habit does
matter to some extent, though, which I
suppose is why `M-.' is still bound to a
find command.





  reply	other threads:[~2019-07-08  0:27 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 [this message]
2019-07-08 20:58       ` Juri Linkov
2019-07-08 21:37         ` Drew Adams
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18bc1649-6d5b-42c4-bb12-3630b0728b9c@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 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.