From: Eli Zaretskii <eliz@gnu.org>
To: chad <yandros@gmail.com>
Cc: emacs-devel@gnu.org, fgunbin@fastmail.fm, spwhitton@spwhitton.name
Subject: Re: Proposal: add a binding for `imenu' under M-g
Date: Fri, 15 Apr 2022 08:51:17 +0300 [thread overview]
Message-ID: <83ilra3ne2.fsf@gnu.org> (raw)
In-Reply-To: <CAO2hHWaMwpZECo0bw4tNwRcTH9An+0Yw7066YVWC8jm39cuGTQ@mail.gmail.com> (message from chad on Thu, 14 Apr 2022 15:03:54 -0400)
> From: chad <yandros@gmail.com>
> Date: Thu, 14 Apr 2022 15:03:54 -0400
> Cc: Sean Whitton <spwhitton@spwhitton.name>,
> Filipp Gunbin <fgunbin@fastmail.fm>,
> EMACS development team <emacs-devel@gnu.org>
>
> From the imenu info node:
>
> If you type ‘M-x imenu’, it reads the name of a definition using the
> minibuffer, then moves point to that definition.[...]
How is this different from what M-. does? or "C-x `"? or even
"C-x b", for that matter?
> The parallel seems pretty clear to me. I tried it out in Org and a couple elisp files, and it felt natural. What am
> I missing? (Honest question; I haven't used imenu much in practice.)
Many Emacs commands eventually "go" someplace. That doesn't yet mean
they should all have a binding with the M-g prefix. I'm saying that
we should perhaps give imenu a different key binding. Why is that
idea being rejected without seriously considering it?
next prev parent reply other threads:[~2022-04-15 5:51 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 [this message]
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
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=83ilra3ne2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=spwhitton@spwhitton.name \
--cc=yandros@gmail.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).