Error: Timed out waiting for language servers to shutdown #8900
Unanswered
crabdancing
asked this question in
General
Replies: 2 comments 1 reply
-
This was an upstream issue in taplo that was fixed. Is your taplo up to date? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you for pointing that out. I'll be sure to bump the version and see what happens. But regardless of what happens, it seems like this workaround should be available for any misbehaving LSP on Helix's side, no? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This is the output I get every time I open a TOML file. Ever. It also hangs for over a second. Which isn't too big a deal, until I'm doing something complicated that involves opening and closing Helix a lot. I am using taplo 0.8.0, and Helix 23.10.
Is there a way to configure Helix to just force kill a language server or language servers in general? I am really fine with the slight risk that maybe some badly designed language server will write to its own config file, and thus corrupt it, or something.
Beta Was this translation helpful? Give feedback.
All reactions