@@ -36,8 +36,6 @@ If you have enough free disk space and you would like to be able to run `x` comm
36
36
rust-analyzer runs in the background, you can also add ` --build-dir build-rust-analyzer ` to the
37
37
` overrideCommand ` to avoid x locking.
38
38
39
- [ `src/etc/rust_analyzer_settings.json` ] : https://github.com/rust-lang/rust/blob/master/src/etc/rust_analyzer_settings.json
40
-
41
39
If running ` ./x check ` on save is inconvenient, in VS Code you can use a [ Build
42
40
Task] instead:
43
41
@@ -74,9 +72,9 @@ Rust-Analyzer to already be configured with Neovim. Steps for this can be
74
72
` neoconf ` is able to read and update Rust-Analyzer settings automatically when the project is
75
73
opened when this file is detected.
76
74
77
- If you're running ` coc.nvim ` , you can use ` :CocLocalConfig ` to create a
78
- ` .vim/coc-settings.json ` and copy the settings from
79
- [ this file ] ( https://github.com/rust-lang/rust/blob/master/ src/etc/rust_analyzer_settings.json) .
75
+ If you're running ` coc.nvim ` ,
76
+ you can use ` :CocLocalConfig ` to create a ` .vim/coc-settings.json ` ,
77
+ and copy the settings from [ ` src/etc/rust_analyzer_settings.json ` ] .
80
78
81
79
Another way is without a plugin, and creating your own logic in your configuration. To do this you
82
80
must translate the JSON to Lua yourself. The translation is 1:1 and fairly straight-forward. It
@@ -347,3 +345,5 @@ You can use `source ./src/etc/completions/x.py.<extension>`
347
345
to load completions for your shell of choice,
348
346
or ` source .\src\etc\completions\x.py.ps1 ` for PowerShell.
349
347
Adding this to your shell's startup script (e.g. ` .bashrc ` ) will automatically load this completion.
348
+
349
+ [ `src/etc/rust_analyzer_settings.json` ] : https://github.com/rust-lang/rust/blob/master/src/etc/rust_analyzer_settings.json
0 commit comments