From b352b90c86e96fe1416f4527c1c88dc2c2c17451 Mon Sep 17 00:00:00 2001 From: Aleksey Kladov Date: Mon, 29 Mar 2021 15:11:31 +0300 Subject: [PATCH] internal: make --log-file more discoverable --- docs/dev/README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/dev/README.md b/docs/dev/README.md index 57162a47de8..dcbab1a1d5d 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md @@ -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 ` 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!