[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* comm
From: |
Stefan Monnier |
Subject: |
bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands |
Date: |
Thu, 03 Aug 2023 09:30:29 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
>>> 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
- bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands, Eli Zaretskii, 2023/08/03
- bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands,
Stefan Monnier <=
- bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands, Stefan Monnier, 2023/08/03
- bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands, Thierry Volpiatto, 2023/08/05
- bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands, Stefan Monnier, 2023/08/15
- bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands, Thierry Volpiatto, 2023/08/15
- bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands, Stefan Monnier, 2023/08/15
- bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands, Thierry Volpiatto, 2023/08/15
bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands, Thierry Volpiatto, 2023/08/05