itsscb/rust-analyzer
1
0
Fork 0
mirror of https://github.com/rust-lang/rust-analyzer.git synced 2025-09-28 11:20:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: remove nit from setup.md

Browse Source
This commit is contained in:
bit-aloo 2025-02-24 23:20:26 +05:30
parent 9df88ff0f6
commit 9526d8bfe9
No known key found for this signature in database
GPG Key ID: 02911B24FDAE81DA
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/book/src/contributing/setup.md
View File

@ -17,10 +17,13 @@ Since rust-analyzer is a Rust project, you will need to install Rust. You can do
**Step 04**: Install the language server locally by running the following command: **Step 04**: Install the language server locally by running the following command:
```sh ```sh
cargo xtask install --server --code-bin code-insiders --dev-rel # Install only the language server
cargo xtask install --server \
--code-bin code-insiders \ # Target a specific editor (code, code-exploration, code-insiders, codium, or code-oss)
--dev-rel # Build in release mode with debug info level 2
``` ```
In the output of this command, there should be a file path provided to the installed binary on your local machine. In the output of this command, there should be a file path provided to the installed binary on your local machine.
It should look something like the following output below: It should look something like the following output below:
``` ```
@ -48,9 +51,12 @@ An example debugging statement could go into the `main_loop.rs` file which can b
```rs ```rs
eprintln!("Hello, world!"); eprintln!("Hello, world!");
``` ```
Now, run the following commands to check the project and reinstall the server:
Now we run `cargo build` and `sh ```sh
cargo xtask install --server --code-bin code-insiders --dev-rel` to reinstall the server. cargo check
cargo xtask install --server --code-bin code-insiders --dev-rel
```
Now on Visual Studio Code Insiders, we should be able to open the Output tab on our terminal and switch to Rust Analyzer Language Server to see the `eprintln!` statement we just wrote. Now on Visual Studio Code Insiders, we should be able to open the Output tab on our terminal and switch to Rust Analyzer Language Server to see the `eprintln!` statement we just wrote.