GNU bug report logs - #76182
31.0.50; minibuffer-allow-text-properties not reliable

Previous Next

Package: emacs;

Reported by: Visuwesh <visuweshm <at> gmail.com>

Date: Mon, 10 Feb 2025 16:29:01 UTC

Severity: normal

Found in version 31.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #17 received at 76182 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: Visuwesh <visuweshm <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 76182 <at> debbugs.gnu.org
Subject: Re: bug#76182: 31.0.50; minibuffer-allow-text-properties not reliable
Date: Wed, 12 Feb 2025 19:10:40 +0200
>> This reminds the recent discussion at
>> https://lists.gnu.org/archive/html/emacs-devel/2024-05/msg00819.html
>> that required documenting this limitation in the docstring of
>> 'imenu-flatten':
>>
>>   Since the values `annotation' and `group' rely on text properties,
>>   you can use them only by selecting candidates from the completions
>>   buffer, not by typing in the minibuffer.  This also means that
>>   if you use `minibuffer-next-completion' (`M-<down>') to select
>>   a completion while point stays in the minibuffer, you need
>>   to customize `minibuffer-completion-auto-choose' to nil that
>>   doesn't insert completion candidates to the minibuffer.
>
> If it is much too difficult to make it reliable in all cases, shouldn't
> this be called out in the docstring of minibuffer-allow-text-properties
> itself?

Agreed, the docstring of minibuffer-allow-text-properties
is the most suitable place to document this limitation.

Regarding to how difficult is to make it reliable,
a better question is whether it's possible at all.

How could you get text properties from the completion candidate,
when you type text in the minibuffer and don't use completion?




This bug report was last modified 83 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.