From: "Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Protesilaos Stavrou <info@protesilaos.com>, 52389@debbugs.gnu.org
Subject: bug#52389: 29.0.50; Imenu does not pop up the Completions eagerly
Date: Fri, 10 Dec 2021 16:16:47 +0100 [thread overview]
Message-ID: <m1lf0strq8.fsf@yahoo.es> (raw)
In-Reply-To: <87mtl8znih.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 10 Dec 2021 12:51:18 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Protesilaos Stavrou <info@protesilaos.com> writes:
>
>> * lisp/imenu.el (imenu-eager-completion-buffer): Set the default value
>> to nil, as that was the intended one.
>> (imenu--completion-buffer): Update the condition to check for a
>> non-nil value to 'imenu-eager-completion-buffer'.
>
> But you're reversing the logic, so that people who have set this to nil
> now won't get an eager pop up?
>
> I don't think we can do that. The documentation (and indeed the name of
> the variable) seems to be wrong, though.
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.
next prev parent reply other threads:[~2021-12-10 15: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 [this message]
2021-12-11 3:25 ` Lars Ingebrigtsen
2021-12-11 20:16 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1lf0strq8.fsf@yahoo.es \
--to=bug-gnu-emacs@gnu.org \
--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 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.