lsp-inlayhints.nvim VS rust-tools.nvim

Thanks for the reply! I also wanted to make it work with clangd, but it won't. I stumbled upon this issue. Maybe you have enough knowledge to figure this out, I don't know how to set up this compilation database. I installed clangd using Mason, and configured it via lspconfig basically the same way as the guy in the issue I linked did. Also, I'm using the newest nightly.

I don't understand why inlay hints must be implemented in a rust-specific plugin. https://github.com/lvimuser/lsp-inlayhints.nvim exists, has support for inline inlay hints (on a separate branch for now) and works with rust (and should work any language server since inlay hints are part of the spec). Am I missing something?

To use inlay hints in typescript an rust you would need this plugin: https://github.com/lvimuser/lsp-inlayhints.nvim It provides example in the readme on how to setup inlay hints for typescript and rust. For now the master brach has "old" inlay hints implementation but there is a branch that implement new one. And of course you will need nightly version for that for now.

https://github.com/lvimuser/lsp-inlayhints.nvim (Multiple langs)

But it doesn't seem to work. I also tried lvimuser/lsp-inlayhints.nvim with no luck. Any advice of how to properly enable this feature when ocamllsp server is attached? Thank you in advance.

I have inlay hints working in nvim with lvimuser/lsp-inlayhints.nvim, no special configuration other than the LspAttach block from their README. The caveat is that your LSP server has to support inlay hints.

The second one might be https://github.com/lvimuser/lsp-inlayhints.nvim

you can use nvim-lspcofig for LSP support, mason.nvim for installing LSP servers, linters, formatters and debug adapters. nvim-cmp for completions, luasnip for snippets, null-ls for configuring your formatter and linters , lsp-inlayhints for inlay hints.

Inlay hints are available through rust-tools.nvim, or lsp-inlayhints.nvim.

iirc, inlay hints aren't supported by nvim's built-in LSP, but you can get them with the inlay-hints plugin: https://github.com/lvimuser/lsp-inlayhints.nvim (if the LSP for omnisharp also supports them)

This is not a robust solution to the problem. I haven't worked on a large Rust project, so I do not know if this is valid for all kinds of Rust projects. Maybe there is a better debugging config setups/plugins out there (simrat39/rust-tools.nvim is one from what I have searched for). I plan to keep using this config, till it breaks; and try and fix it when it does.

rust-tools is what I'm currently using, https://github.com/simrat39/rust-tools.nvim

I then took the snippet from, I also changed the path to the correct install path of the above. https://github.com/simrat39/rust-tools.nvim/wiki/Debugging

rust-tools.nvim and crates.nvim should be helpful for you. :)

I'd start with nvim-treesitter, nvim-lspconfig, and use rust-tools.nvim as an accelerant. Any remaining advice I'd have is about Neovim but not about Rust. That advice would also be mostly questions of taste for this-or-that decisions.

Are you using https://github.com/simrat39/rust-tools.nvim/ ?

TIL that if you install Rust via Homebrew (like brew install rust), auto formatting (or more specifically, lsp formatting) doesn't work properly. I used both Rust Analyzer and rust-tools) to setup rust lsp and configured it with tons of options, thinking maybe something will work but somehow, one thing never did - auto formatting. This is the command I use for setting up auto formatting via lsp:

neovim + native lsp with rust-tools.nvim, running nixos so I use flakes for my dev environments

I opened an issue https://github.com/simrat39/rust-tools.nvim/issues/369 after searching for such behavior in existing ones. But I also ask here in case it's a known problem.