Re: [PATCH] Re: Other details about completion.

[Juri Linkov]

>>>> 1. zstyle ':completion:*' menu select interactive
>>>>    - allows typing a letter that immediately
>>>>    updates the list of completions.
>>>
>>> Yes, but that may be complicated because completions calls a function
>>> that will try first to complete the common part and then update the
>>> completions. (Look what happens when you press a letter and tab
>>> immediately). There are few ways to go around that without braking half
>>> of the Universe. Look where I added the code for the
>>> completion-auto-help visible and always... there is where the magic
>>> happens.
>>>
>>> Maybe you will find a better way to manage what you want.
>>
>> Indeed, this is why I proposed to create zcomplete-mode
>> that works exactly like icomplete-mode, but updates completions
>> in the Completions window instead of the minibuffer.
>
> IIRC Helm already uses that approach?

Helm uses own buffer, not the standard *Completions* buffer.

>>>> 2. zstyle ':completion:*' menu select search
>>>>    - shows the prompt "isearch:" where typing letters
>>>>    searches them incrementally in the list of completions.
>>>
>>>>> 2) it will be simpler to implement with
>>>>> icomplete and that family of completion engines.
>>>>
>>>> Agreed, this would be the best thing to do.
>>>
>>> For that we have fido and similes... What we are trying to improve a bit
>>> is the default completion engine. Then the user will choose fido, ido or
>>> something external... it is up to him.
>>
>> fido, ido and others use the minibuffer, but zcomplete-mode will use
>> the Completions window.
>
> Then my question will be... what's the advantage/difference from the
> user point of view compared with putting the completions in the
> minibuffer like icomplete/fido/ivy/ido do?

The advantage is that it's easy to switch to the *Completions* buffer,
and use all available navigation keys and isearch capabilities.