@@ -24,20 +24,20 @@ You can also install the hook as a step of running `./x.py setup`!
24
24
` rust-analyzer ` can help you check and format your code whenever you save
25
25
a file. By default, ` rust-analyzer ` runs the ` cargo check ` and ` rustfmt `
26
26
commands, but you can override these commands to use more adapted versions
27
- of these tools when hacking on ` rustc ` . For example, ` x.py setup ` will prompt
27
+ of these tools when hacking on ` rustc ` . For example, ` x.py setup vscode ` will prompt
28
28
you to create a ` .vscode/settings.json ` file which will configure Visual Studio code.
29
29
This will ask ` rust-analyzer ` to use ` ./x.py check ` to check the sources, and the
30
30
stage 0 rustfmt to format them.
31
- The recommended ` rust-analyzer ` settings live at [ ` src/etc/vscode_settings .json ` ] .
31
+ The recommended ` rust-analyzer ` settings live at [ ` src/etc/rust_analyzer_settings .json ` ] .
32
32
33
33
If you have enough free disk space and you would like to be able to run ` x.py ` commands while
34
34
rust-analyzer runs in the background, you can also add ` --build-dir build-rust-analyzer ` to the
35
35
` overrideCommand ` to avoid x.py locking.
36
36
37
37
If you're running ` coc.nvim ` , you can use ` :CocLocalConfig ` to create a
38
- ` .vim/coc-settings.json ` and copy the settings from [ ` src/etc/vscode_settings .json ` ] .
38
+ ` .vim/coc-settings.json ` and copy the settings from [ ` src/etc/rust_analyzer_settings .json ` ] .
39
39
40
- [ `src/etc/vscode_settings .json` ] : https://github.com/rust-lang/rust/blob/master/src/etc/vscode_settings .json
40
+ [ `src/etc/rust_analyzer_settings .json` ] : https://github.com/rust-lang/rust/blob/master/src/etc/rust_analyzer_settings .json
41
41
42
42
If running ` ./x.py check ` on save is inconvenient, in VS Code you can use a [ Build
43
43
Task] instead:
0 commit comments