From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eshel Yaron <me@eshelyaron.com>
Cc: michael_heerdegen@web.de, pipcet@protonmail.com,
Arash Esbati <arash@gnu.org>,
72787@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#72787: 31.0.50; Invalid describe-function completion candidates
Date: Thu, 17 Oct 2024 13:03:30 -0400 [thread overview]
Message-ID: <jwvjze6n08o.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m14j5ga21j.fsf@macbookpro-1.home> (Eshel Yaron's message of "Sun, 13 Oct 2024 09:35:04 +0200")
>> Actually, it's not so much for the case where you know you want to see
>> `foo-bar` (which should be handled by `help-enable-symbol-autoload`
>> already) but also to let you discover that there might be a `foo-bar`
>> because there's a `foo-`.
>
> I see, so this is meant as a hint that should aid with discoverability.
Yes. Sometimes that works via *Completions* (i.e. it requires the user
to see the `foo-` entry and understand that it means there's something
with this prefix), but sometimes it works without it, e.g. when you do
`C-h f trac-ch TAB` which completes to `track-changes-` after which
the next TAB will show you the possible completions.
> Perhaps annotating these prefix candidates could make that more obvious:
> I'm not sure that seeing "foo-" in *Completions* immediately suggests
> "try to complete this prefix to see more candidates".
Agreed.
> Personally I don't see this use case as important enough to break the
> invariant that completion candidates are valid inputs, so I'd go a
> different route. The ability to load possibly-relevant libraries from
> within the minibuffer is great, but I think that providing a command
> that does that on demand would provide the same benefits. Basically,
> you would press a key when you want to check if some unloaded maybe
> library defines something relevant. Such a command could take into
> account the current minibuffer input, so it can be as efficient as the
> current facility. I can share a prototype if that sounds intriguing.
The intention of the current behavior is to be a bit more transparent
and try to approximate the illusion of having `C-h o` (I personally
never use `C-h v` of `C-h f` any more) give information about any
function/variable defined in any of the installed packages, rather than
only in the currently loaded set of files.
Stefan
next prev parent reply other threads:[~2024-10-17 17:03 UTC|newest]
Thread overview: 22+ 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
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-16 20:31 ` Arash Esbati
2024-10-13 7:35 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-17 17:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvjze6n08o.fsf-monnier+emacs@gnu.org \
--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 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.