Thorsten Ball a56a260778 Add ability to specify binary path/args for rust-analyzer (#9293) ... This fixes #9292 by adding a section to the language server settings that allows users to specify the binary path and arguments with which to start up a language server. Example user settings for `rust-analyzer`: ```json { "lsp": { "rust-analyzer": { "binary": { "path": "/Users/thorstenball/tmp/rust-analyzer-aarch64-apple-darwin", "arguments": ["--no-log-buffering"] } } } } ``` Constraints: * Right now this only allows ABSOLUTE paths. * This is only used by `rust-analyzer` integration right now, but the setting can be used for other language servers. We just need to update the adapters to also respect that setting. Release Notes: - Added ability to specify `rust-analyzer` binary `path` (must be absolute) and `arguments` in user settings. Example: `{"lsp": {"rust-analyzer": {"binary": {"path": "/my/abs/path/rust-analyzer", "arguments": ["--no-log-buffering"] }}}}` ([#9292](https://github.com/zed-industries/zed/issues/9292)). Co-authored-by: Ricard Mallafre <rikitzzz@gmail.com>		2024-03-13 18:42:03 +01:00
..
src	Add ability to specify binary path/args for rust-analyzer (#9293)	2024-03-13 18:42:03 +01:00
Cargo.toml	Provide wasm extensions with APIs needed for using pre-installed LSP binaries (#9085)	2024-03-08 17:18:06 -05:00
LICENSE-GPL	chore: Extract languages from zed crate (#8270)	2024-02-23 15:56:08 +01:00