From 5934eeda558d233a4e67e1ad16475a563f9a3d6e Mon Sep 17 00:00:00 2001 From: Joel Daniel Rico Date: Mon, 17 Jun 2024 02:48:37 -0700 Subject: feat: add `toggleLSPLogs` command add `toggleLSPLogs` command update docs to reflect new command --- src/tools/rust-analyzer/docs/dev/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/tools/rust-analyzer/docs/dev') diff --git a/src/tools/rust-analyzer/docs/dev/README.md b/src/tools/rust-analyzer/docs/dev/README.md index 8897f02e277..002b8ba2a66 100644 --- a/src/tools/rust-analyzer/docs/dev/README.md +++ b/src/tools/rust-analyzer/docs/dev/README.md @@ -145,7 +145,7 @@ To log all communication between the server and the client, there are two choice ``` env RA_LOG=lsp_server=debug code . ``` -* You can log on the client side, by enabling `"rust-analyzer.trace.server": "verbose"` workspace setting. +* You can log on the client side, by the `rust-analyzer: Toggle LSP Logs` command or 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! -- cgit 1.4.1-3-g733a5