unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: chad <yandros@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: EMACS development team <emacs-devel@gnu.org>,
	Filipp Gunbin <fgunbin@fastmail.fm>,
	Sean Whitton <spwhitton@spwhitton.name>
Subject: Re: Proposal: add a binding for `imenu' under M-g
Date: Wed, 20 Apr 2022 13:19:49 -0400	[thread overview]
Message-ID: <CAO2hHWZVQSbC5OXwDYSTtderSTFaJQPd4MSzPHFwRoUtC_uEEA@mail.gmail.com> (raw)
In-Reply-To: <83czhctbkw.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

I don't have a strong opinion in this area, as someone who doesn't use
imenu very much, but I feel like I was asked to support my intuition, so:

On Wed, Apr 20, 2022 at 4:15 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > While M-g would mean "go".  And stuff like "M-g g", "M-g c", they
> > request input only to go somewhere.  imenu falls in this category -
> > request input (select from completions) and go there.
>
> To me, imenu is a facility to find definitions of functions, so it is
> conceptually very similar to M-. and other such features.  We don't
> perceive M-. as a "go" command, do we?
>

 I *do* feel like C-u M-. is a "go" command, similar to the others, since
it prompts for input and "goes" there, but I also understand that the
difference between "go" and "find/search" is intentionally fuzzy in emacs.

I think C-x ` is another good example of a command that fits in the concept
that I recall suggested for M-g back when it was added, and I notice that
it actually has a binding in M-g, which I think supports the idea of M-g as
"go" and also that it's ok to have some longstanding "go" functionality be
bound both inside M-g and outside.

I hope that helps,
~Chad

[-- Attachment #2: Type: text/html, Size: 1734 bytes --]

  parent reply	other threads:[~2022-04-20 17:19 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 15:36 Proposal: add a binding for `imenu' under M-g Sean Whitton
2022-04-14 14:16 ` Sean Whitton
2022-04-14 16:14   ` Eli Zaretskii
2022-04-14 17:21     ` Filipp Gunbin
2022-04-14 18:00       ` Sean Whitton
2022-04-14 18:12       ` Eli Zaretskii
2022-04-14 19:03         ` chad
2022-04-15  5:51           ` Eli Zaretskii
2022-04-15  6:45             ` Sean Whitton
2022-04-15  6:50               ` Eli Zaretskii
2022-04-15 17:16                 ` Howard Melman
2022-04-15 17:16                 ` Howard Melman
2022-04-20  5:15                 ` Sean Whitton
2022-04-20  6:38                   ` Eli Zaretskii
2022-04-20  8:02                     ` Filipp Gunbin
2022-04-20  8:15                       ` Eli Zaretskii
2022-04-20 10:27                         ` Filipp Gunbin
2022-04-20 11:55                         ` Brian Cully
2022-04-20 12:10                         ` Stefan Monnier
2022-04-20 15:53                           ` John Yates
2022-04-21 13:14                             ` Stefan Monnier
2022-04-20 16:43                           ` Sean Whitton
2022-04-20 17:19                         ` chad [this message]
2022-04-20 20:54                         ` Kévin Le Gouguec
2022-04-21  7:20                           ` Juri Linkov
2022-04-21 15:36                             ` [External] : " Drew Adams
2022-04-21 17:50                             ` Howard Melman
2022-04-22  3:37                               ` Sean Whitton
2022-04-21 17:54                             ` Kévin Le Gouguec
2022-04-21 19:03                             ` Sean Whitton
2022-04-21 19:01                     ` Sean Whitton
2022-04-14 19:37         ` Sean Whitton
2022-04-14 19:52           ` [External] : " Drew Adams
2022-04-19 14:21           ` Stephen Leake
2022-04-14 19:47         ` [External] : " Drew Adams
2022-04-14 16:24   ` Filipp Gunbin

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=CAO2hHWZVQSbC5OXwDYSTtderSTFaJQPd4MSzPHFwRoUtC_uEEA@mail.gmail.com \
    --to=yandros@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=fgunbin@fastmail.fm \
    --cc=spwhitton@spwhitton.name \
    /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).