8235: internal: make --log-file more discoverable r=matklad a=matklad

bors r+
🤖

Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
This commit is contained in:
bors[bot] 2021-03-29 12:12:36 +00:00 committed by GitHub
commit 80ebd0108c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -135,12 +135,15 @@ panel and select `rust-analyzer`. This shows `eprintln!` as well. Note that
To log all communication between the server and the client, there are two choices:
* you can log on the server side, by running something like
* You can log on the server side, by running something like
```
env RA_LOG=lsp_server=debug code .
```
* you can log on the client side, by enabling `"rust-analyzer.trace.server":
By default, logs go to stderr, `--log-file <PATH>` CLI argument overrides
that.
* You can log on the client side, by enabling `"rust-analyzer.trace.server":
"verbose"` workspace setting. These logs are shown in a separate tab in the
output and could be used with LSP inspector. Kudos to
[@DJMcNab](https://github.com/DJMcNab) for setting this awesome infra up!