@@ -24,20 +24,20 @@ You can also install the hook as a step of running `./x.py setup`!
2424` rust-analyzer ` can help you check and format your code whenever you save
2525a file. By default, ` rust-analyzer ` runs the ` cargo check ` and ` rustfmt `
2626commands, 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
2828you to create a ` .vscode/settings.json ` file which will configure Visual Studio code.
2929This will ask ` rust-analyzer ` to use ` ./x.py check ` to check the sources, and the
3030stage 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 ` ] .
3232
3333If you have enough free disk space and you would like to be able to run ` x.py ` commands while
3434rust-analyzer runs in the background, you can also add ` --build-dir build-rust-analyzer ` to the
3535` overrideCommand ` to avoid x.py locking.
3636
3737If 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 ` ] .
3939
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
4141
4242If running ` ./x.py check ` on save is inconvenient, in VS Code you can use a [ Build
4343Task] instead:
0 commit comments