Re: feature/completions-highlight-modifications e3c5b99 3/6: Add completions-highlight-mode initial implementation.

[Ergus <spacibba@aol.com>]

On Sat, Nov 21, 2020 at 09:30:17PM +0200, Juri Linkov wrote:
>>>> Maybe we should look more how zsh behaves... and try to mimic that as
>>>> much as possible. Because it is already pretty consisten
>>>
>>>Does zsh use arrow keys to navigate in completions?
>>>How then it's possible to get previous/next history item (up/down arrows),
>>>and move the cursor in the command line (left/right arrows)?
>>
>> Similar to what we are doing.
>>
>> 1) When NO completions shown: previous/next history and so on.
>> 2) When completions are shown: navigate completions.
>>
>> Completions are only shown after a "tab request" 1->2 (unlike
>> incomplete)
>
>Trying to mimic the 'zsh' behavior is a good thing.  Using
>'zsh' as a reference, what do you think about naming the package
>'zcomplete'.
>
>> If you type any letter completions disappear, inserts a space and then
>> the letter, so
>>
>> backspace just hides completions (deletes the inserted space), so goes
>> from 2->1 easily (unlike *Completions*).
>
>If you want to emulate the 'zsh' behavior, then much simpler approach
>would be to allow TAB to pop-up the completions buffer, i.e. to display
>and switch to it.  Then all motion keys will be available by default.
>To display the cursor in the minibuffer is still possible by using
>'(cursor-in-echo-area t)'.  RET will insert the completion under point
>to the minibuffer.  Any self-inserting key could switch back
>to the minibuffer and insert its character.
>
Hi Juri:

Could you try it now please?

I am wondering that with this new behavior it is a bit more like zsh but
diverges a bit too much from the current default emacs completion, so
making this default will be virtually impossible. And my real objective
was to improve the default completion; not make a new one.

IMO we may reconsider if we should go in the direction of commit
60a1003aee or in the one of c7c47e78e6.

Best,
Ergus