mirror of
https://github.com/rust-lang/rust-analyzer
synced 2025-01-13 21:54:42 +00:00
internal: make --log-file more discoverable
This commit is contained in:
parent
ae7de296ae
commit
b352b90c86
1 changed files with 5 additions and 2 deletions
|
@ -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:
|
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 .
|
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
|
"verbose"` workspace setting. These logs are shown in a separate tab in the
|
||||||
output and could be used with LSP inspector. Kudos to
|
output and could be used with LSP inspector. Kudos to
|
||||||
[@DJMcNab](https://github.com/DJMcNab) for setting this awesome infra up!
|
[@DJMcNab](https://github.com/DJMcNab) for setting this awesome infra up!
|
||||||
|
|
Loading…
Reference in a new issue