Skip to content

Commit 1147d90

Browse files
committed
Removed coc since there is already a section and cleaned up wording.
1 parent 1d7bdef commit 1147d90

File tree

1 file changed

+10
-12
lines changed

1 file changed

+10
-12
lines changed

src/building/suggested.md

+10-12
Original file line numberDiff line numberDiff line change
@@ -28,16 +28,14 @@ This will ask `rust-analyzer` to use `./x.py check` to check the sources, and th
2828
stage 0 rustfmt to format them.
2929

3030

31-
For Neovim users there are several options for configuring for rustc. You can use the native LSP
32-
server and make your own logic for changing the rust-analyzer configuration to the above. You can
33-
also use [nlsp-settings](https://github.com/tamago324/nlsp-settings.nvim), which allows for
34-
project-local configuration files. This plugin allows for the above JSON to be directly put in to
35-
a file located at `rust/.nlsp-settings/rust_analyzer.json`. If you use
36-
[coc-rust-analyzer](https://github.com/fannheyward/coc-rust-analyzer) you can also use the above
37-
JSON, but placed in `rust/.vim/coc-settings.json`.
31+
For Neovim users there are several options for configuring for rustc. The easiest way is by using
32+
[nlsp-settings](https://github.com/tamago324/nlsp-settings.nvim), which allows for project-local
33+
configuration files with the native LSP. First install the plugin by however you manage your
34+
plugins. Then run `:LspSettings local rust_analyzer` to create a JSON configuration file. Then
35+
just paste the above JSON in.
3836

39-
Below is the Lua needed to configure the native Neovim LSP the same as the above VSCode
40-
configuration
37+
Another way is without a plugin, and creating your own logic in your configuration. The required
38+
Lua for doing so is below.
4139

4240
```lua
4341
{
@@ -72,13 +70,13 @@ configuration
7270
}
7371
```
7472

73+
If you're running `coc.nvim`, you can use `:CocLocalConfig` to create a
74+
`.vim/coc-settings.json` and copy the settings from [this file](https://github.com/rust-lang/rust/blob/master/src/etc/vscode_settings.json).
75+
7576
If you have enough free disk space and you would like to be able to run `x.py` commands while
7677
rust-analyzer runs in the background, you can also add `--build-dir build-rust-analyzer` to the
7778
`overrideCommand` to avoid x.py locking.
7879

79-
If you're running `coc.nvim`, you can use `:CocLocalConfig` to create a
80-
`.vim/coc-settings.json` and copy the settings from [this file](https://github.com/rust-lang/rust/blob/master/src/etc/vscode_settings.json).
81-
8280
If running `./x.py check` on save is inconvenient, in VS Code you can use a [Build
8381
Task] instead:
8482

0 commit comments

Comments
 (0)