Unnamed repository; edit this file 'description' to name the repository.
Diffstat (limited to 'docs/user/manual.adoc')
| -rw-r--r-- | docs/user/manual.adoc | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/docs/user/manual.adoc b/docs/user/manual.adoc index 6521b6d8b3..8e6c53d0c5 100644 --- a/docs/user/manual.adoc +++ b/docs/user/manual.adoc @@ -376,7 +376,7 @@ If you're running Neovim 0.10 or later, you can enable inlay hints via `on_attac ---- lspconfig.rust_analyzer.setup({ on_attach = function(client, bufnr) - vim.lsp.inlay_hint.enable(bufnr) + vim.lsp.inlay_hint.enable(true, { bufnr = bufnr }) end }) ---- @@ -787,8 +787,6 @@ There are three ways to feed `rust-project.json` to rust-analyzer: Relative paths are interpreted relative to `rust-project.json` file location or (for inline JSON) relative to `rootUri`. -See https://github.com/rust-analyzer/rust-project.json-example for a small example. - You can set the `RA_LOG` environment variable to `rust_analyzer=info` to inspect how rust-analyzer handles config and project loading. Note that calls to `cargo check` are disabled when using `rust-project.json` by default, so compilation errors and warnings will no longer be sent to your LSP client. |