Unnamed repository; edit this file 'description' to name the repository.
Merge #11042
11042: minor: clarify RA_LOG env var troubleshooting r=lnicola a=Veykril
cc https://github.com/rust-analyzer/rust-analyzer/pull/10261
Co-authored-by: Lukas Wirth <[email protected]>
| -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 cfcad7c66b..1335f8df7c 100644 --- a/docs/user/manual.adoc +++ b/docs/user/manual.adoc @@ -447,7 +447,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.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`. |