[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Updating *Completions* as you type
From: |
Björn Bidar |
Subject: |
Re: Updating *Completions* as you type |
Date: |
Sat, 14 Oct 2023 22:26:52 +0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
>> > IIUC what you mean by "asynchronous completion", it is a terrible
>> > idea. How can anyone type text without getting immediate feedback for
>> > what he/she typed? When I sometimes see this (due to network delays
>> > or system load or whatever), it is a terrible UX.
>>
>> By asynchronous completion, I just mean being able to type, and trigger
>> completion, and have completions appear incrementally as they are
>> computed, without interfering with you continuing to type. I don't
>> think that stops immediate feedback for typing.
>
> If it's asynchronous, then how can we make sure the feedback is
> immediate?
The feedback updates while typing but doesn't show until the delay set
by the user has passed to show the suggestions again.
If the feedback hasn't updated by the time the user stops typing then
the old state is shown similar to how the feedback is when the
completion is synchronous.
I most cases I think the feedback updates as fast as the major mode can
update the buffer to pass it e.g. to an internal function or language
server/or alike.
In cases of external programs parsing the just updated buffer the
completion can be nearly asynchronous already.
Re: Updating *Completions* as you type, Juri Linkov, 2023/10/13