Ivan Yonchovski
Ivan Yonchovski
Test with lsp-start-plain.el as described in bug template.
I believe the issue is a combination of our code and the slowness of the fontlock of c-mode. Most likely we should use a smarter way to check if the...
The following piece of code avoids the issue: ``` (add-hook 'lsp-lua-language-server-after-open-hook (lambda () (-> (lsp-workspaces) (cl-first) (lsp--workspace-server-capabilities) (lsp:server-capabilities-completion-provider?) (lsp:set-completion-options-trigger-characters? [" " "." ":" "(" "'" "\"" "[" "," "#" "*"...
@ericdallo @sebastiansturm - any clue?
@rieje as I requested in the original issue, can you test with the latest versions of everything, preferably with `M-x lsp-start-plain`?
> Odd, we do implement support for that notification [here ](https://github.com/emacs-lsp/lsp-mode/blob/master/lsp-mode.el#L6340), or do we need to handle a server request differently from a server notification @yyoncho ? @ericdallo this is...
Does it go away after C-g or multiple C-g?
To me, it looks like something that has to be investigated on the server side first. Can you ask in their channels?
To me, 1. looks good enough. Is there anything against this approach?
> It's pretty good but it pollutes the buffer a bit (related locations are shown at all times). Isn't that what we want? Or you mean that it is visible...