From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: My usage of imenu is broken.
Date: Tue, 28 May 2024 10:53:18 +0000 [thread overview]
Message-ID: <ZlW3nsSdZCQNqZFr@ACM> (raw)
Hello, Emacs.
imenu no longer works for me. The imenu page in the Emacs manual says
the command [imenu] always displays the whole list of valid names.
This is not true. When I type C-c i (my binding for imenu) I see no
such list. When I additionally type TAB I still see no such list. All
I see is *Rescan*, Function, and Variable. I think the manual should be
fixed.
The manual talks about "flatten"ing without explaining what this means.
The NEWS item doesn't explain it either. I think this should be fixed.
On typing C-c i, I used to be able to type the first characters of a
function name and complete it with TAB in the minibuffer. This no
longer works. It doesn't work even if I set imenu-flatten to t.
Instead I've got to type boilerplate first. This is unacceptable to me.
How do I get the old behaviour back, please? Why doesn't the NEWS item
say how to get back the old behaviour?
What happened to Emacs's convention that new facilities are disabled by
default to begin with, and only made the default after positive
experience with their use?
--
Alan Mackenzie (Nuremberg, Germany).
next reply other threads:[~2024-05-28 10:53 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 10:53 Alan Mackenzie [this message]
2024-05-28 11:34 ` My usage of imenu is broken Eli Zaretskii
2024-05-28 13:57 ` Alan Mackenzie
2024-05-28 18:29 ` Eli Zaretskii
2024-05-28 20:46 ` Alan Mackenzie
2024-05-28 21:28 ` Stefan Monnier
2024-05-29 6:04 ` Juri Linkov
2024-05-29 11:31 ` Eli Zaretskii
2024-05-29 5:38 ` Yuan Fu
2024-05-28 21:55 ` Stefan Monnier
2024-05-29 11:16 ` Subversion of user chosen major mode by Emacs. [Was: My usage of imenu is broken.] Alan Mackenzie
2024-05-29 11:43 ` Dmitry Gutov
2024-05-29 12:51 ` Subversion of user chosen major mode by Emacs Alan Mackenzie
2024-05-29 16:08 ` Dmitry Gutov
2024-05-29 16:38 ` Eli Zaretskii
2024-05-29 17:56 ` Dmitry Gutov
2024-05-29 19:22 ` Alan Mackenzie
2024-05-29 19:45 ` Andrea Corallo
2024-05-29 19:59 ` Alan Mackenzie
2024-05-30 5:01 ` Eli Zaretskii
2024-05-30 11:02 ` Alan Mackenzie
2024-05-29 22:10 ` Dmitry Gutov
2024-05-30 5:51 ` Eli Zaretskii
2024-05-30 5:44 ` Eli Zaretskii
2024-05-29 12:41 ` Subversion of user chosen major mode by Emacs. [Was: My usage of imenu is broken.] Eli Zaretskii
2024-05-29 13:29 ` Subversion of user chosen major mode by Emacs Alan Mackenzie
2024-05-29 14:20 ` Eli Zaretskii
2024-05-29 15:04 ` Stefan Monnier
2024-05-29 19:17 ` Subversion of user chosen major mode by Emacs. [Was: My usage of imenu is broken.] Eli Zaretskii
2024-05-30 1:32 ` Stefan Monnier
2024-05-30 5:25 ` Eli Zaretskii
2024-05-30 7:39 ` Po Lu
2024-05-30 7:53 ` Eli Zaretskii
2024-05-30 14:18 ` Stefan Monnier
2024-05-30 14:33 ` Po Lu
2024-05-30 15:08 ` Stefan Monnier
2024-05-30 14:56 ` Eli Zaretskii
2024-05-30 15:12 ` Stefan Monnier
2024-05-30 15:29 ` Alan Mackenzie
2024-05-30 18:30 ` Stefan Monnier
2024-05-30 16:06 ` Eli Zaretskii
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=ZlW3nsSdZCQNqZFr@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
/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).