rust-analyzer

mirror of https://github.com/rust-lang/rust-analyzer.git synced 2025-09-26 20:09:19 +00:00

History

Michael Bolin e81a47b8eb Remove executeCommandProvider: apply_code_action. This appears to have been introduced ages ago in `be742a5877` but has since been removed. As it stands, it is problematic if multiple instances of the rust-analyzer LSP are launched during the same VS Code session because VS Code complains about multiple LSP servers trying to register the same command. Most LSP servers workaround this by parameterizing the command by the process id. For example, this is where `rls` does this: `ff0b9057c8/rls/src/server/mod.rs (L413-L421)` Though `apply_code_action` does not seems to be used, so it seems better to delete it than to parameterize it.	2019-07-10 22:49:35 -07:00
..
dev	Remove executeCommandProvider: apply_code_action.	2019-07-10 22:49:35 -07:00
user	More details on how to set up coc	2019-06-18 09:25:59 -05:00

Michael Bolin e81a47b8eb Remove executeCommandProvider: apply_code_action.

This appears to have been introduced ages ago in
be742a5877
but has since been removed.

As it stands, it is problematic if multiple instances of the
rust-analyzer LSP are launched during the same VS Code session because
VS Code complains about multiple LSP servers trying to register the
same command.

Most LSP servers workaround this by parameterizing the command by the
process id. For example, this is where `rls` does this:

ff0b9057c8/rls/src/server/mod.rs (L413-L421)

Though `apply_code_action` does not seems to be used, so it seems better
to delete it than to parameterize it.

2019-07-10 22:49:35 -07:00

dev Remove executeCommandProvider: apply_code_action. 2019-07-10 22:49:35 -07:00

user More details on how to set up coc 2019-06-18 09:25:59 -05:00