Skip to content

Commit 5f48eb9

Browse files
committed
Fix line lengths
1 parent ee3c3a8 commit 5f48eb9

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

src/building/suggested.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -57,9 +57,16 @@ in your `.vscode/settings.json` file. This will ask `rust-analyzer` to use
5757
`./x.py check` to check the sources, and the stage 0 rustfmt to format them.
5858

5959

60-
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`.
61-
62-
Below is the Lua needed to configure the native Neovim LSP the same as the above VSCode configuration
60+
For Neovim users there are several options for configuring for rustc. You can use the native LSP
61+
server and make your own logic for changing the rust-analyzer configuration to the above. You can
62+
also use [nlsp-settings](https://github.com/tamago324/nlsp-settings.nvim), which allows for
63+
project-local configuration files. This plugin allows for the above JSON to be directly put in to
64+
a file located at `rust/.nlsp-settings/rust_analyzer.json`. If you use
65+
[coc-rust-analyzer](https://github.com/fannheyward/coc-rust-analyzer) you can also use the above
66+
JSON, but placed in `rust/.vim/coc-settings.json`.
67+
68+
Below is the Lua needed to configure the native Neovim LSP the same as the above VSCode
69+
configuration
6370

6471
```lua
6572
{

0 commit comments

Comments
 (0)