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: manual.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -479,7 +479,7 @@ You can follow instructions for installing <<rust-analyzer-language-server-binar
479
479
== Troubleshooting
480
480
481
481
Start with looking at the rust-analyzer version.
482
-
Try **Rust Analyzer: Show RA Version** in VS Code (using **Command Palette** feature typically activated by Ctrl+Shift+P) or `rust-analyzer --version` in the command line.
482
+
Try **rust-analyzer: Show RA Version** in VS Code (using **Command Palette** feature typically activated by Ctrl+Shift+P) or `rust-analyzer --version` in the command line.
483
483
If the date is more than a week ago, it's better to update rust-analyzer version.
484
484
485
485
The next thing to check would be panic messages in rust-analyzer's log.
@@ -492,7 +492,7 @@ To fully capture LSP messages between the editor and the server, set `"rust-anal
492
492
The root cause for many "`nothing works`" problems is that rust-analyzer fails to understand the project structure.
493
493
To debug that, first note the `rust-analyzer` section in the status bar.
494
494
If it has an error icon and red, that's the problem (hover will have somewhat helpful error message).
495
-
**Rust Analyzer: Status** prints dependency information for the current file.
495
+
**rust-analyzer: Status** prints dependency information for the current file.
496
496
Finally, `RA_LOG=project_model=debug` enables verbose logs during project loading.
497
497
498
498
If rust-analyzer outright crashes, try running `rust-analyzer analysis-stats /path/to/project/directory/` on the command line.
0 commit comments