Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Diagnostics not cleared when LspStop is used in Neovim #110

Open
ronandalton opened this issue Sep 16, 2024 · 2 comments
Open

Diagnostics not cleared when LspStop is used in Neovim #110

ronandalton opened this issue Sep 16, 2024 · 2 comments

Comments

@ronandalton
Copy link

When using :LspStop (provided by nvim-lspconfig) in Neovim, the diagnostics are cleared for other LSPs attached to the buffer, but not for typos-lsp. Furthermore, doing :LspStart doesn't seem to make typos-lsp start working again. Interestingly, :LspInfo still shows the LSP as being attached even after issuing :LspStop, so that might be part of the issue.

Neovim version: 0.10.1

Thanks

@tekumara
Copy link
Owner

I can see the Neovim lsp client sends the exit notification here. The exit notification tells the server process to stop. But it looks like this isn't happening.

@christoph-heiss
Copy link

Since I just stumbled upon this myself:

You can workaround this for now using :LspStop <id> ++force, which forcibly kills the language server and in turn, also removes all diagnostics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants