bug#81537: 32.0.50; Fixing icomplete-in-buffer requiring users to advice-add

Juri Linkov [03/Aug  8:07pm +03] wrote:
>>> Shouldn't the UI of icomplete-in-buffer be the same as the UI
>>> of icomplete in the minibuffer?  That is, only when the user
>>> types TAB, it should display the *Completions* buffer,
>>> either in the minibuffer or in the regular buffer.
>>> But otherwise on typing characters it should display inline
>>> candidates immediately, without requiring to type TAB,
>>> i.e. something like 'completion-preview-mode' already does.
>>
>> Do you mean after the *second* tab?  I think the first should definitely
>> only display the inline candidates.
>
> I meant an option to display in-buffer icomplete completions without
> typing TAB, i.e. like in the minibuffer.  But this would be a new feature.

I think someone who wants that can use some advice.

Do you think the second-tab behaviour I've implemented is unwanted?

-- 
Sean Whitton