From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "Protesilaos Stavrou" <info@protesilaos.com>,
52389@debbugs.gnu.org, "Daniel Martín" <mardani29@yahoo.es>
Subject: bug#52389: 29.0.50; Imenu does not pop up the Completions eagerly
Date: Sat, 11 Dec 2021 22:16:01 +0200 [thread overview]
Message-ID: <86h7belwxq.fsf@mail.linkov.net> (raw)
In-Reply-To: <87h7bfx1p6.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 11 Dec 2021 04:25:25 +0100")
>> I think the safest way to solve this long-standing problem without
>> surprising users is to introduce a new variable whose logic is handled
>> correctly, and mark imenu-eager-completion-buffer as deprecated.
>
> Sounds good to me. (The new variable could be an alias of the old name,
> but have a name with the opposite meaning, and then things would
> continue to work for everybody.)
This is a good opportunity for generalization.
Like there is icomplete-show-matches-on-no-input,
would it be possible to create a new user option
e.g. minibuffer-auto-show-completions, and allow
to customize what commands should use it.
Then it could be like completion-auto-select
recently proposed by Philip.
next prev parent reply other threads:[~2021-12-11 20:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 13:32 bug#52389: 29.0.50; Imenu does not pop up the Completions eagerly Protesilaos Stavrou
2021-12-10 11:51 ` Lars Ingebrigtsen
2021-12-10 15:16 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-11 3:25 ` Lars Ingebrigtsen
2021-12-11 20:16 ` Juri Linkov [this message]
2021-12-12 4:58 ` Lars Ingebrigtsen
2021-12-12 6:09 ` Protesilaos Stavrou
2021-12-12 17:36 ` Juri Linkov
2021-12-13 7:20 ` Protesilaos Stavrou
2021-12-13 8:53 ` Juri Linkov
2021-12-17 11:57 ` Protesilaos Stavrou
2021-12-17 12:34 ` André A. Gomes
2021-12-17 12:55 ` Eli Zaretskii
2021-12-18 7:44 ` 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=86h7belwxq.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=52389@debbugs.gnu.org \
--cc=info@protesilaos.com \
--cc=larsi@gnus.org \
--cc=mardani29@yahoo.es \
/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).