Skip to content

Commit 1d7bdef

Browse files
committed
Fix line lengths
1 parent 92befb7 commit 1d7bdef

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

src/building/suggested.md

+10-3
Original file line numberDiff line numberDiff line change
@@ -28,9 +28,16 @@ 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 server and make your own logic for changing the rust-analyzer configuration to the above. You can also use [nlsp-settings](https://github.com/tamago324/nlsp-settings.nvim), which allows for project-local configuration files. This plugin allows for the above JSON to be directly put in to a file located at `rust/.nlsp-settings/rust_analyzer.json`. If you use [coc-rust-analyzer](https://github.com/fannheyward/coc-rust-analyzer) you can also use the above JSON, but placed in `rust/.vim/coc-settings.json`.
32-
33-
Below is the Lua needed to configure the native Neovim LSP the same as the above VSCode configuration
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`.
38+
39+
Below is the Lua needed to configure the native Neovim LSP the same as the above VSCode
40+
configuration
3441

3542
```lua
3643
{

0 commit comments

Comments
 (0)