emacs-devel
[Top][All Lists]
Advanced

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

Re: Could ivy minibuffer stay where it is?


From: Basil L. Contovounesios
Subject: Re: Could ivy minibuffer stay where it is?
Date: Fri, 06 Nov 2020 21:17:04 +0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Jean Louis <bugs@gnu.support> writes:

> * Basil L. Contovounesios <contovob@tcd.ie> [2020-11-06 18:21]:
>> Jean Louis <bugs@gnu.support> writes:
>> 
>> > Oleh, is there a setting for Ivy that minibuffer stays where it is?
>> >
>> > You may see the difference between:
>> >
>> > counsel-M-x
>> >
>> > and
>> >
>> > helm-M-x as this one creates 2 buffers, one for selection while
>> > minibuffer stays where it is. This is my preferred way of work. As
>> > user is typing and should not move his eyes or focus from familiar
>> > place in this case minibuffer.
>> >
>> > Could you consider adding such option that prompt remains in the
>> > minibuffer while selection is above minibuffer?
>> 
>> Ivy was explicitly designed with the minibuffer in mind, just like
>> built-in minibuffer completion.  That said, it's possible to customise
>> where completions appear.  For example, in-buffer completion is
>> displayed in an overlay at point, not in the minibuffer.
>> See e.g. the following for more information:
>> 
>> - https://github.com/abo-abo/swiper/wiki/ivy-display-function
>> - ivy-display-functions-alist
>> - ivy-display-functions-props
>> - https://github.com/tumashu/ivy-posframe
>
> That is it! Definitely good solution.
>
> Can that function `ivy-display-function-window' be included in ivy on
> GNU ELPA?

I don't know, that's Oleh's call.  I vaguely remember a preference for
showcasing these potential customisations in the wiki, rather than
maintaining them as part of Ivy, but I'm not sure.

-- 
Basil



reply via email to

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