From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Thierry Volpiatto <thievol@posteo.net>
Cc: Eli Zaretskii <eliz@gnu.org>, 64902@debbugs.gnu.org
Subject: bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands
Date: Thu, 03 Aug 2023 09:30:29 -0400 [thread overview]
Message-ID: <jwvy1is8dw5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <873518xaoz.fsf@posteo.net> (Thierry Volpiatto's message of "Fri, 28 Jul 2023 16:16:42 +0000")
>>> The problem is that with Helm completion I have an extra unknown
>>> symbol on top of list when I start typing (this is expected when
>>> require-match is non-nil),
>> Could you characterize this "unknown symbol" a bit more? I'm having
>> trouble guessing why/how/where `confirm` would have such an effect.
> In Helm, if require-match is 'confirm, when you write in minibuffer something
> that doesn't match one of the candidates this string is appended on top
> of list and is prefixed (with display prop) with [?]. By contrast when
> require-match is nil nothing is appended on top of list and pressing RET
> doesn't exit minibuffer (helm-buffer is empty in such case).
> IOW the behavior of require-match is the same than with vanilla Emacs.
I see. So IIUC every piece works "correctly", but since it's *very*
rare to want to use this ?-prefixed option in the case of
`describe-function`, it looks/feels like a bug.
The core of the problem is that in the normal UI, `confirm` is very
lightweight (you'll basically only notice it when you do try to enter
the name of a function that's not defined) whereas in the Helm UI it's
harder to hide it.
And I guess for other cases (like `find-file`) the use of the ?-prefixed
option is sufficiently common to deserve being more visible?
Stefan
next prev parent reply other threads:[~2023-08-03 13:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 14:52 bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands Thierry Volpiatto
2023-07-27 16:57 ` Eli Zaretskii
2023-07-28 3:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-28 5:41 ` Thierry Volpiatto
2023-07-28 14:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-28 16:16 ` Thierry Volpiatto
2023-07-29 5:28 ` Thierry Volpiatto
2023-08-03 8:28 ` Eli Zaretskii
2023-08-03 13:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-08-03 21:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-05 6:51 ` Thierry Volpiatto
2023-08-15 14:23 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-15 15:41 ` Thierry Volpiatto
2023-08-15 16:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-15 17:00 ` Thierry Volpiatto
2023-08-05 6:39 ` Thierry Volpiatto
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=jwvy1is8dw5.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=64902@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=thievol@posteo.net \
/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.