Closed dariusf closed 1 month ago
Hi @dariusf , I'm sorry to hear of this problem, it shouldn't happen!
Do you mind sharing coq-lsp
client and server versions, and how to reproduce?
I was not able to reproduce this problem in my testing, but indeed I am sure there are cases we didn't anticipate.
By the way, I agree this "red button" is annoying, in fact I have the same problem with rust-analyzer
being red often, and I'm not surprised as we got inspired by rust-analyzer
when designing the toolbar.
We will likely remove this button and favor the new LanguageStatusItem API.
No worries, and good to know! 😄
Here's my environment and the steps I took:
Coq LSP VS Code extension: v0.1.10
opam switch 5.1.0
; coq-lsp server is not installedcode .
in a directory with just an empty test.md fileCoq LSP Server client: couldn't create connection to server.
I see thanks, indeed I can reproduce. Will work on a fix ASAP.
For now you can workaround this by right clicking on the toolbar, and selecting hide. Use instead the new indicator in the language section (bottom-right corner {}
symbol, then pin)
Great, thank you!
Thank you for developing coq-lsp!
I use many opam switches, most of which don't have coq-lsp installed.
With the new activation criteria (#737), when I open a project unrelated to Coq, e.g. containing only LaTeX and a Markdown readme, the extension activates and shows an error message about failing to connect to the LSP server, along with a rather obtrusive, persistent red section in the status bar.
Would it be possible to not activate the extension, or perhaps not show errors, if connecting to coq-lsp fails because it isn't installed?