diff options
| author | Lukas Wirth <lukastw97@gmail.com> | 2021-12-17 18:07:01 +0100 |
|---|---|---|
| committer | Lukas Wirth <lukastw97@gmail.com> | 2021-12-17 18:08:40 +0100 |
| commit | 1cd40a408ae7fca3d286667360e46c530034c3ff (patch) | |
| tree | a74e0cdf27991a8d2ef45ecfdc7ad15ec7841709 | |
| parent | 6674756c07a4175d5c2f2cd4539bf1d76bc704f1 (diff) | |
| download | rust-1cd40a408ae7fca3d286667360e46c530034c3ff.tar.gz rust-1cd40a408ae7fca3d286667360e46c530034c3ff.zip | |
minor: clarify RA_LOG env var troubleshooting
| -rw-r--r-- | docs/user/manual.adoc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/user/manual.adoc b/docs/user/manual.adoc index 4fbe2379c3d..c0d12851481 100644 --- a/docs/user/manual.adoc +++ b/docs/user/manual.adoc @@ -445,7 +445,7 @@ If the date is more than a week ago, it's better to update rust-analyzer version The next thing to check would be panic messages in rust-analyzer's log. Log messages are printed to stderr, in VS Code you can see then in the `Output > Rust Analyzer Language Server` tab of the panel. -To see more logs, set the `RA_LOG=info` environment variable. +To see more logs, set the `RA_LOG=info` environment variable, this can be done either by setting the environment variable manually or by using `rust-analyzer.rust-analyzer.server.extraEnv`, note that both of these approaches require the server to be restarted. To fully capture LSP messages between the editor and the server, set `"rust-analyzer.trace.server": "verbose"` config and check `Output > Rust Analyzer Language Server Trace`. |