aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAleksey Kladov <[email protected]>2020-03-24 09:31:52 +0000
committerAleksey Kladov <[email protected]>2020-03-24 09:40:16 +0000
commit681c6eeeebce1745f42c0e2937cb7b6be1ea9f85 (patch)
tree63e5c79021686859c1359147fd774fb5c0dca99a
parent1d6024e460219d6d012c800107dc8169cf613ec2 (diff)
Add troubleshooting secion
-rw-r--r--docs/user/readme.adoc10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/user/readme.adoc b/docs/user/readme.adoc
index 0dfc12b52..e00d14dfb 100644
--- a/docs/user/readme.adoc
+++ b/docs/user/readme.adoc
@@ -98,6 +98,16 @@ You'll need Cargo, nodejs and npm for this.
98 98
99Note that installing via `xtask install` does not work for VS Code Remote, instead you'll need to install the `.vsix` manually. 99Note that installing via `xtask install` does not work for VS Code Remote, instead you'll need to install the `.vsix` manually.
100 100
101==== Troubleshooting
102
103Here are some useful self-diagnostic commands:
104
105* **Rust Analyzer: Show RA Version** shows the version of `rust-analyzer` binary
106* **Rust Analyzer: Status** prints some statistics about the server, like the few latest LSP requests
107* To enable server-side logging, run with `env RUST_LOG=info` and see `Output > Rust Analyzer Language Server` in VS Code's panel.
108* To log all LSP requests, add `"rust-analyzer.trace.server": "verbose"` to the settings and look for `Server Trace` in the panel.
109* To enable client-side logging, add `"rust-analyzer.trace.extension": true` to the settings and open the `Console` tab of VS Code developer tools.
110
101=== Language Server Binary 111=== Language Server Binary
102 112
103Other editors generally require `rust-analyzer` binary to be in `$PATH`. 113Other editors generally require `rust-analyzer` binary to be in `$PATH`.