From c514440e8410a01f7129c782f4902261f4bbe53c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C4=B0smail=20Ar=C4=B1l=C4=B1k?= Date: Fri, 14 Jul 2023 15:03:32 +0300 Subject: [PATCH] fix(suggested): remove an unnecessary and confusing statement This statement is not about Visual Studio Code; it is about Neovim and it is already in that section. And it is also confusing for a VS Code user. So I think it is better to remove it. --- src/building/suggested.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/building/suggested.md b/src/building/suggested.md index 156546ffd..0da3f60cf 100644 --- a/src/building/suggested.md +++ b/src/building/suggested.md @@ -36,9 +36,6 @@ If you have enough free disk space and you would like to be able to run `x` comm rust-analyzer runs in the background, you can also add `--build-dir build-rust-analyzer` to the `overrideCommand` to avoid x locking. -If you're running `coc.nvim`, you can use `:CocLocalConfig` to create a -`.vim/coc-settings.json` and copy the settings from [`src/etc/rust_analyzer_settings.json`]. - [`src/etc/rust_analyzer_settings.json`]: https://github.com/rust-lang/rust/blob/master/src/etc/rust_analyzer_settings.json If running `./x check` on save is inconvenient, in VS Code you can use a [Build