From f809687956931f1ae1f37128a77d5930457fb977 Mon Sep 17 00:00:00 2001 From: Joshua Nelson Date: Sun, 3 Jul 2022 02:17:39 -0400 Subject: [PATCH] Suggest a separate build directory for rust-analyzer (#1378) --- src/doc/rustc-dev-guide/src/building/suggested.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/doc/rustc-dev-guide/src/building/suggested.md b/src/doc/rustc-dev-guide/src/building/suggested.md index 8accc681ecca..e08ca6b22e0e 100644 --- a/src/doc/rustc-dev-guide/src/building/suggested.md +++ b/src/doc/rustc-dev-guide/src/building/suggested.md @@ -61,6 +61,10 @@ in your `.vscode/settings.json` file. This will ask `rust-analyzer` to use > a triple is `x86_64-unknown-linux-gnu`. An easy way to check your target triple > is to run `rustc -vV` and checking the `host` value of its output. +If you have enough free disk space and you would like to be able to run `x.py` commands while +rust-analyzer runs in the background, you can also add `--build-dir build-rust-analyzer` to the +`overrideCommand` to avoid x.py locking. + If you're running `coc.nvim`, you can use `:CocLocalConfig` to create a `.vim/coc-settings.json` and enter the same settings as above, but replacing `editor.formatOnSave: true,` with