-
Notifications
You must be signed in to change notification settings - Fork 326
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
Shutdown routine #30
Comments
I'm almost done in switching to lsp4j, which is a much more completed and tested implementation. I hope all this issues with the protocol bindings are going away very soon. |
OK, cool |
lsp4j is not on the table anymore, let's fix this. |
@gabro let me know if you have started with this. Otherwise I'll try to fix it. VS Code does a trick by killing server process if it didn't reply to |
I noticed that server responses with an error to the
shutdown
request:shutdown
request is not supposed to have any parameters, so I think that the underlying LSP library doesn't handle it well.It causes some extra lags in Atom (atom/atom-languageclient#119) and I suspect after this response server never receives an
exit
request. By the way, I didn't find howexit
is handled in the server.The text was updated successfully, but these errors were encountered: