You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/book/src/contributing/README.md
+6-3
Original file line number
Diff line number
Diff line change
@@ -140,9 +140,10 @@ By default, log goes to stderr, but the stderr itself is processed by VS Code.
140
140
`--log-file <PATH>` CLI argument allows logging to file.
141
141
Setting the `RA_LOG_FILE=<PATH>` environment variable will also log to file, it will also override `--log-file`.
142
142
143
-
To see stderr in the running VS Code instance, go to the "Output" tab of the panel and select `Rust Analyzer Client`.
143
+
To see the server stderr output in the running VS Code instance, go to the "Output" tab of the panel
144
+
and select `rust-analyzer Language Server`.
144
145
This shows `eprintln!` as well.
145
-
Note that `stdout` is used for the actual protocol, so `println!`will break things.
146
+
Note that `stdout` is used by LSP messages, so using `println!`—or anything that writes to `stdout`—will break rust-analyzer!
146
147
147
148
To log all communication between the server and the client, there are two choices:
148
149
@@ -153,9 +154,11 @@ To log all communication between the server and the client, there are two choice
153
154
```
154
155
155
156
* You can log on the client side, by the `rust-analyzer: Toggle LSP Logs` command or enabling `"rust-analyzer.trace.server": "verbose"` workspace setting.
156
-
These logs are shown in a separate tab in the output and could be used with LSP inspector.
157
+
These logs are shown in a separate tab named `rust-analyzer LSP Trace`in the output and could be used with LSP inspector.
157
158
Kudos to [@DJMcNab](https://github.com/DJMcNab) for setting this awesome infra up!
158
159
160
+
Finally there are the logs of the VSCode extension itself which go into the `rust-analyzer Extension` output tab.
161
+
159
162
There are also several VS Code commands which might be of interest:
160
163
161
164
*`rust-analyzer: Status` shows some memory-usage statistics.
0 commit comments