aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2020-12-23 07:47:40 +0000
committerGitHub <[email protected]>2020-12-23 07:47:40 +0000
commit58b6763f206b80a3000eb3c7642181fa5fb98229 (patch)
tree65c66a9bec9b74049ca588ffb3d4a47337486280 /docs
parentf7f85cdd8d0660e3556c15864efd6158f114e343 (diff)
parent7c07bb63814671f88677c08ddd75862338e40330 (diff)
Merge #7012
7012: Document, how to view config in effect r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
Diffstat (limited to 'docs')
-rw-r--r--docs/user/manual.adoc3
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/user/manual.adoc b/docs/user/manual.adoc
index 40f10972f..e3082d584 100644
--- a/docs/user/manual.adoc
+++ b/docs/user/manual.adoc
@@ -302,6 +302,9 @@ If the LSP binary is not available, GNOME Builder can install it when opening a
302rust-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. 302rust-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.
303Please consult your editor's documentation to learn how to configure LSP servers. 303Please consult your editor's documentation to learn how to configure LSP servers.
304 304
305To verify which configuration is actually used by rust-analyzer, set `RA_LOG` environment variable to `rust_analyzer=info` and look for config-related messages.
306Logs should show both the JSON that rust-analyzer sees as well as the updated config.
307
305This is the list of config options rust-analyzer supports: 308This is the list of config options rust-analyzer supports:
306 309
307include::./generated_config.adoc[] 310include::./generated_config.adoc[]