Skip to content

Commit 9b8b76e

Browse files
committed
Add link to vscode settings in Rust repo
1 parent df5aee0 commit 9b8b76e

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

src/building/suggested.md

+4-1
Original file line numberDiff line numberDiff line change
@@ -26,13 +26,16 @@ of these tools when hacking on `rustc`. For example, `x.py setup` will prompt
2626
you to create a `.vscode/settings.json` file which will configure Visual Studio code.
2727
This will ask `rust-analyzer` to use `./x.py check` to check the sources, and the
2828
stage 0 rustfmt to format them.
29+
The recommended `rust-analyzer` settings live at [`src/etc/vscode_settings.json`].
2930

3031
If you have enough free disk space and you would like to be able to run `x.py` commands while
3132
rust-analyzer runs in the background, you can also add `--build-dir build-rust-analyzer` to the
3233
`overrideCommand` to avoid x.py locking.
3334

3435
If 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

3740
If running `./x.py check` on save is inconvenient, in VS Code you can use a [Build
3841
Task] instead:

0 commit comments

Comments
 (0)