aboutsummaryrefslogtreecommitdiff
path: root/docs/dev/README.md
diff options
context:
space:
mode:
authorAleksey Kladov <[email protected]>2020-05-11 18:14:12 +0100
committerAleksey Kladov <[email protected]>2020-05-11 18:16:00 +0100
commit72e229fcb35f6056183f681e0d16c4fff8e5e381 (patch)
tree77a45256d7eedac1ab8b53d35fd036ded3d35522 /docs/dev/README.md
parent05399250d47cdceffbf1ded08983b13a9dcc87c1 (diff)
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.
Diffstat (limited to 'docs/dev/README.md')
-rw-r--r--docs/dev/README.md2
1 files changed, 1 insertions, 1 deletions
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
134 134
135* you can log on the server side, by running something like 135* you can log on the server side, by running something like
136 ``` 136 ```
137 env RUST_LOG=gen_lsp_server=trace code . 137 env RA_LOG=gen_lsp_server=trace code .
138 ``` 138 ```
139 139
140* you can log on the client side, by enabling `"rust-analyzer.trace.server": 140* you can log on the client side, by enabling `"rust-analyzer.trace.server":