-
Notifications
You must be signed in to change notification settings - Fork 305
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
LspStopServer: Stop all and stop specific #1491
LspStopServer: Stop all and stop specific #1491
Conversation
c83e89a
to
b9ed71a
Compare
b9ed71a
to
0b0db77
Compare
could you fix the lint issue? |
What is the issue?
Update. |
Vim documentation says that default values for arguments are fair game. I can change Do you want to make this change? |
We should make the change. Not sure if older versions of vim will have issues. Some devs use the one that ships with OS and they are not fan of updating to latest version. Specially for those using LTS versions that barely update vim. |
fc05014
to
92ebd4a
Compare
It is convenient to be able to stop all LSP servers, regardless of the currently active buffer. Also, it seems confusing that when a server name is specified, it is only stopped if it is also one handling the current buffer type. I would imagine it is quite rare to have more than one server handing a specific buffer type. And if one explicitly specified a name, it seems reasonable to stop this particular server, regardless of the currently active buffer.
92ebd4a
to
6e35c23
Compare
Rebased, addressed two linter issues, and added quotes around server names. @prabirshrestha Please, take a look. |
Merged. Thanks! |
It is convenient to be able to stop all LSP servers, regardless of the currently active buffer. Also, it seems confusing that when a server name is specified, it is only stopped if it is also one handling the current buffer type. I would imagine it is quite rare to have more than one server handing a specific buffer type. And if one explicitly specified a name, it seems reasonable to stop this particular server, regardless of the currently active buffer.
It is convenient to be able to stop all LSP servers, regardless of the currently active buffer.
Also, it seems confusing that when a server name is specified, it is only stopped if it is also one handling the current buffer type. I would imagine it is quite rare to have more than one server handing a specific buffer type. And if one explicitly specified a name, it seems reasonable to stop this particular server, regardless of the currently active buffer.