diff options
Diffstat (limited to 'docs/user/manual.adoc')
-rw-r--r-- | docs/user/manual.adoc | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/docs/user/manual.adoc b/docs/user/manual.adoc index 9d4f52a93..1ec6e81bb 100644 --- a/docs/user/manual.adoc +++ b/docs/user/manual.adoc | |||
@@ -95,6 +95,23 @@ If you don't want to be asked for `Download now` every day when the new nightly | |||
95 | 95 | ||
96 | NOTE: Nightly extension should **only** be installed via the `Download now` action from VS Code. | 96 | NOTE: Nightly extension should **only** be installed via the `Download now` action from VS Code. |
97 | 97 | ||
98 | ==== Manual installation | ||
99 | |||
100 | Alternatively, procure both `rust-analyzer.vsix` and your platform's matching `rust-analyzer-{platform}`, for example from the | ||
101 | https://github.com/rust-analyzer/rust-analyzer/releases[releases] page. | ||
102 | |||
103 | Install the extension with the `Extensions: Install from VSIX` command within VS Code, or from the command line via: | ||
104 | [source] | ||
105 | ---- | ||
106 | $ code --install-extension /path/to/rust-analyzer.vsix | ||
107 | ---- | ||
108 | |||
109 | Copy the `rust-analyzer-{platform}` binary anywhere, then add the path to your settings.json, for example: | ||
110 | [source,json] | ||
111 | ---- | ||
112 | { "rust-analyzer.serverPath": "~/.local/bin/rust-analyzer-linux" } | ||
113 | ---- | ||
114 | |||
98 | ==== Building From Source | 115 | ==== Building From Source |
99 | 116 | ||
100 | Alternatively, both the server and the Code plugin can be installed from source: | 117 | Alternatively, both the server and the Code plugin can be installed from source: |
@@ -272,6 +289,8 @@ GNOME Builder 3.37.1 and newer has native `rust-analyzer` support. If the LSP bi | |||
272 | 289 | ||
273 | == Configuration | 290 | == Configuration |
274 | 291 | ||
292 | **Source:** https://github.com/rust-analyzer/rust-analyzer/blob/master/crates/rust-analyzer/src/config.rs[config.rs] | ||
293 | |||
275 | rust-analyzer is configured via LSP messages, which means that it's up to the editor to decide on the exact format and location of configuration files. | 294 | rust-analyzer is configured via LSP messages, which means that it's up to the editor to decide on the exact format and location of configuration files. |
276 | Please consult your editor's documentation to learn how to configure LSP servers. | 295 | Please consult your editor's documentation to learn how to configure LSP servers. |
277 | 296 | ||