From: Eshel Yaron via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, pipcet@protonmail.com,
Arash Esbati <arash@gnu.org>,
72787@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#72787: 31.0.50; Invalid describe-function completion candidates
Date: Fri, 11 Oct 2024 11:18:49 +0200 [thread overview]
Message-ID: <m1frp3atfq.fsf@macbookpro-1.home> (raw)
In-Reply-To: <m1ttdjb12b.fsf@macbookpro-1.home> (Eshel Yaron's message of "Fri, 11 Oct 2024 08:34:04 +0200")
Eshel Yaron <me@eshelyaron.com> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Arash Esbati <arash@gnu.org>
>>>
>>> Is it possible to revert this change on master as well until a new
>>> working patch is available? IIUC, Stefan noted upthread:
>>>
>>> I think this report makes it clear that
>>> 45ae4de0e7ce99c88c62f940f605bca693b8e33f should not have gone to
>>> `emacs-30` but to `master`. AFAIK it did not fix a regression or even
>>> a user-visible bug.
>>>
>>> The current behavior is somewhat annoying.
>>
>> AFAIU, Stefan later explained that this is a feature, but maybe I
>> misunderstood him. See
>>
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=73473#16
>
> AFAIU, the feature here would be loading library foo just in time for
> you to get help about symbol foo-bar. But the way this feature is
> currently implemented is by including incorrect completion candidates.
> That's not a feature, that's an implementation artifact, which
> unfortunately happens to create an unpleasant UX :/
>
> So I suggest doing one of the following:
>
> - implement the feature differently, without this side-effect; or
> - make it opt-in; or at least
> - allow users to opt-out.
Correction: I forgot that there's already a way to opt-out, by setting
help-enable-completion-autoload to nil.
Cheers,
Eshel
next prev parent reply other threads:[~2024-10-11 9:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 10:54 bug#72787: 31.0.50; Invalid describe-function completion candidates Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-24 11:15 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-26 1:41 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-26 2:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-26 23:57 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-31 9:54 ` Eli Zaretskii
2024-09-01 17:41 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-01 18:00 ` Eli Zaretskii
2024-10-10 4:56 ` Arash Esbati
2024-10-10 6:34 ` Eli Zaretskii
2024-10-11 6:34 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-11 9:18 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-10-11 14:22 ` Arash Esbati
2024-10-11 22:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-12 9:41 ` Arash Esbati
2024-10-13 0:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-14 19:23 ` Arash Esbati
2024-10-14 21:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-13 7:35 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-11 23:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=m1frp3atfq.fsf@macbookpro-1.home \
--to=bug-gnu-emacs@gnu.org \
--cc=72787@debbugs.gnu.org \
--cc=arash@gnu.org \
--cc=eliz@gnu.org \
--cc=me@eshelyaron.com \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=pipcet@protonmail.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).