File tree Expand file tree Collapse file tree 1 file changed +4
-1
lines changed Expand file tree Collapse file tree 1 file changed +4
-1
lines changed Original file line number Diff line number Diff line change @@ -26,13 +26,16 @@ of these tools when hacking on `rustc`. For example, `x.py setup` will prompt
2626you to create a ` .vscode/settings.json ` file which will configure Visual Studio code.
2727This will ask ` rust-analyzer ` to use ` ./x.py check ` to check the sources, and the
2828stage 0 rustfmt to format them.
29+ The recommended ` rust-analyzer ` settings live at [ ` src/etc/vscode_settings.json ` ] .
2930
3031If you have enough free disk space and you would like to be able to run ` x.py ` commands while
3132rust-analyzer runs in the background, you can also add ` --build-dir build-rust-analyzer ` to the
3233` overrideCommand ` to avoid x.py locking.
3334
3435If you're running ` coc.nvim ` , you can use ` :CocLocalConfig ` to create a
35- ` .vim/coc-settings.json ` and copy the settings from [ this file] ( https://github.com/rust-lang/rust/blob/master/src/etc/vscode_settings.json ) .
36+ ` .vim/coc-settings.json ` and copy the settings from [ ` src/etc/vscode_settings.json ` ] .
37+
38+ [ `src/etc/vscode_settings.json` ] : https://github.com/rust-lang/rust/blob/master/src/etc/vscode_settings.json
3639
3740If running ` ./x.py check ` on save is inconvenient, in VS Code you can use a [ Build
3841Task] instead:
You can’t perform that action at this time.
0 commit comments