From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Protesilaos Stavrou <info@protesilaos.com>,
juri@linkov.net, 52389@debbugs.gnu.org, mardani29@yahoo.es
Subject: bug#52389: 29.0.50; Imenu does not pop up the Completions eagerly
Date: Sat, 18 Dec 2021 08:44:50 +0100 [thread overview]
Message-ID: <87bl1exsp9.fsf@gnus.org> (raw)
In-Reply-To: <835yrne6h6.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 17 Dec 2021 14:55:17 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> +(defcustom imenu-no-eager-completion-buffer t
>> + "If non-nil, do not eagerly popup the completion buffer."
>
> The doc string should go on to explain what does it mean to "eagerly
> popup a buffer". It is not self-evident.
>
> (Yes, I know this was in the original text, but while we are at that,
> we might as well fix that omission.)
And I don't think we should call a variable
`imenu-no-eager-completion-buffer' -- it's very confusing.
`imenu-inhibit-eager-completion-buffer' is better.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-12-18 7:44 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
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 [this message]
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=87bl1exsp9.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=52389@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=info@protesilaos.com \
--cc=juri@linkov.net \
--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.