From 72e229fcb35f6056183f681e0d16c4fff8e5e381 Mon Sep 17 00:00:00 2001 From: Aleksey Kladov Date: Mon, 11 May 2020 19:14:12 +0200 Subject: Use RA_LOG instead of RUST_LOG for logging RUST_LOG might be set up for debugging the user's problem, slowing down rust-analyzer considerably. That's the same reason why rustc uses RUSTC_LOG. --- docs/dev/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/dev/README.md') diff --git a/docs/dev/README.md b/docs/dev/README.md index f230dc1db..a20ead0b6 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md @@ -134,7 +134,7 @@ To log all communication between the server and the client, there are two choice * you can log on the server side, by running something like ``` - env RUST_LOG=gen_lsp_server=trace code . + env RA_LOG=gen_lsp_server=trace code . ``` * you can log on the client side, by enabling `"rust-analyzer.trace.server": -- cgit v1.2.3