-
Notifications
You must be signed in to change notification settings - Fork 29k
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
Restart language server – a generic solution #76405
Comments
Where is this at homies? it's been 2 years. |
+1 to what @kealjones-wk said. |
I looked into this when I added the Restart command for ESLint. At the end I decided against it since all ESLint commands should usually be found by typing What I did do is the following: I improved the LSP libraries so that a restart command is easy to implement. Just call One additional note: if you hook any special request / notification handlers after onReady() you need to do the same after a restart since the listeners might to start in a different state. |
I will close the issue since the coding happened in |
Quite often, I encounter a situation where some language server misbehaves and I have to Reload Window as the only workaround. I don't like doing that, though, as it also stops all running tasks, restarts terminals, etc.
I know some language servers implement their own "restart language server" command, for example, TypeScript has Restart TS Server and there are some third-party feature requests like microsoft/vscode-cpptools#1152 or microsoft/vscode-go#2324 but would there be a way to provide this as a VSCode-wide command that works across extensions?
I can imagine that a new API would need to be proposed that the extensions would need to implement, and I'm not sure how that works, but from the user perspective I'd very much appreciate the feature.
The text was updated successfully, but these errors were encountered: