joaotavora
commented
6 years ago too slow (completions take a while to return?) to be useable.
Well, there's only so much we can do on eglot's side to "speed up" completions. We can't really speed them up, only keep the interface as responsible as possible while we frantically make requests and hope the responses arrive in time.
In that sense, even with company-capf (my preferred method of working with company since it works also without company, and thus with any future completion frontend) you can do it like this:
- Make a synchronous request that is cancelled as soon as the user types something. You can use
while-no-inputfor that. - If the request isn't cancelled then return whatever the return value is.
- If the request is cancelled return nil. The underlying request is still going to the server and the server will still respond, but that response is dirty so it is discarded.
This may or not be what your example is doing (I didn't fully understand it), but is the only way. I have tested this approach successfully in a common Lisp IDE called SLY. See its sly-eval function with is similar to jsonrpc-request.
In short, this is more than probably more correctly implemented in jsonrpc.el, by adding a cancel-on-input and cancel-on-input-retval parameters to jsonrpc-request and then using those parameters from eglot-completion-at-point.
jojojames
terlar
Hi, thanks for the package!
Working with completion-at-point/company-capf, it seems like completions are being done synchronously. Playing around with Emacs' codebase (window.c) and cquery, it seems there is slight lag/stutter when typing.
I gave a shot here but it seems too slow (typing latency is faster but completions take a while to return?) to be useable.