[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: |
Thierry Volpiatto |
Subject: |
bug#64902: 30.0.50; REQUIRE-MATCH completing-read arg in describe-* commands |
Date: |
Fri, 28 Jul 2023 05:41:00 +0000 |
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> `completing-read` REQUIRE-MATCH arg in describe-variable == t,
>>> describe-symbol == t and describe-function == 'confirm ?
>>>
>>> I see no reasons why `describe-function` uses 'confirm but maybe I am
>>> missing something?
>>
>> Stefan (CC'ed) made that change last September, and it looks
>> deliberate.
>>
>> Stefan?
>
> I'm not sure what was the situation that motivated it, because I failed
> to write it in the comment or commit message :-(
> I suspect it might have been when a function is advised but not yet defined.
Hmm, how could this happen? The problem is that with Helm completion I
have an extra unknow symbol on top of list when I start typing (this is
expected when require-match is non-nil), not very
annoying but I am pretty sure I will have bug reports about this.
>
> Stefan
--
Thierry
signature.asc
Description: PGP signature