GNU bug report logs -
#76461
31.0.50; CRM tries to insert candidate in prompt read-only zone
Previous Next
Reported by: Thierry Volpiatto <thievol <at> posteo.net>
Date: Fri, 21 Feb 2025 08:08:02 UTC
Severity: normal
Tags: patch
Found in version 31.0.50
Fixed in version 30.2
Done: Dmitry Gutov <dmitry <at> gutov.dev>
Bug is archived. No further changes may be made.
Full log
Message #30 received at 76461-done <at> debbugs.gnu.org (full text, mbox):
Version: 30.2
On 28/02/2025 07:54, Thierry Volpiatto wrote:
> Dmitry Gutov <dmitry <at> gutov.dev> writes:
>
>> On 27/02/2025 20:33, Juri Linkov wrote:
>>> Maybe Dmitry could confirm if this is the right fix
>>> for completing-read-multiple recently fixed in
>>> bug#48356 and bug#76010.
>>
>> It seems okay, thanks. Though it depends on the prompt always being a
>> field, and the only field in the minibuffer. I don't know if that will
>> hold for ever, but it seems to be the case currently.
>
> Is it possible for a user to setup a minibuffer prompt with no properties at
> all? Don't think so, but just asking.
Probably not in CRM, since here we control how the minibuffer is setup,
but ultimately we have hooks there as well, so a determined enough user
could break it, of course.
>> Here's a slightly different fix which seems to behave the same in the
>> test scenario. I'm happy with whichever of the two you prefer.
>
> Yours seems better, thanks.
Pushed to the emacs-30 branch, thank you for testing.
https://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-30&id=8091772767666f2c671a8ba481d50859388152db
This bug report was last modified 160 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.