You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/building/suggested.md
+4-1Lines changed: 4 additions & 1 deletion
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
26
26
you to create a `.vscode/settings.json` file which will configure Visual Studio code.
27
27
This will ask `rust-analyzer` to use `./x.py check` to check the sources, and the
28
28
stage 0 rustfmt to format them.
29
+
The recommended `rust-analyzer` settings live at [`src/etc/vscode_settings.json`].
29
30
30
31
If you have enough free disk space and you would like to be able to run `x.py` commands while
31
32
rust-analyzer runs in the background, you can also add `--build-dir build-rust-analyzer` to the
32
33
`overrideCommand` to avoid x.py locking.
33
34
34
35
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`].
0 commit comments