emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: master@head: completing-read behavior change?


From: T.V Raman
Subject: Re: master@head: completing-read behavior change?
Date: Thu, 23 Jan 2020 06:44:28 -0800
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Dmitry Gutov <address@hidden> writes:

will check icomplete when I have time, I frankly dont remember any more
whether I handle it. What would be a simple test usage for icomplete? I
have ido, flx-ido and ido-ubiquitous (can never remember its new name)
active, so as you can guess my emacs world is complex.> Hi T.V.,
>
> On 23.01.2020 3:03, T.V Raman wrote:
>> Fix is here for the curious:-)
>> https://github.com/tvraman/emacspeak/blob/master/lisp/emacspeak-ido.el#L85
>
> You haven't answered my question about support for icomplete-mode. Do
> you only support Ido?
>
> I'm happy you made it work, but I think it would be better to handle
> the general approach. Meaning, instead of hardcoding the names of
> (private) variables, scan the minibuffer, look for the overlays with
> after-string, order by 'priority', and read their contents one after
> another.
>
> The new set-minibuffer-message feature uses the same approach if
> minibuffer is active. Although, in that case, you could advise this 
> function, or set an alternative handler via the set-message-function
> variable (also just added in Emacs 27).
>

-- 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]