Re: Updating *Completions* as you type

[Michael Albinus]

Eli Zaretskii <eliz@gnu.org> writes:

Hi Eli,

>> >> +    (while-no-input
>> >> +      (let ((non-essential t))
>> >                 ^^^^^^^^^^^^^^^
>> > Why?
>>
>> This I borrowed from zcomplete.  It seems sensible, since
>> non-essential's docstring says:
>>
>>   E.g., it can be used to prevent Tramp from prompting the user for a
>>   password when we are [...] displaying possible completions before the
>>   user even asked for it.
>
> So completion on remote files will not be able to benefit from this?

No, remote files are not kicked out by this. non-essential just prevents
to open a *new* connection during the completion phase, when there
doesn't exist one already. If the connection exists already,
non-essential isn't relevant.

However, I believe it isn't needed here. Updating *Completions* will
happen only if a completion package is active. And they bind
non-essential already.

Best regards, Michael.