rust-tools.nvim VS lsp-status.nvim

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.

https://github.com/nvim-lua/lsp-status.nvim do not have this issue (I completely disabled it before trying this one to avoid conflicts).

I use lsp-status to show the language server indexing progress

I use https://github.com/nvim-lua/lsp-status.nvim to get LSP diagnostic info for status lines / etc. This might be of interest if only in seeing its inner workings.

[lsp-status](https://github.com/nvim-lua/lsp-status.nvim) that's used by the statusline plugin I use ([bubbly.nvim](https://github.com/datwaft/bubbly.nvim)) to populate lsp diagnostic info in the status bar (ex. 2 errors, 50 warnings, etc). I only added it per suggestion of the plugin, so it's quite possible you wouldn't need it.

lsp-status.nvim - Language Server Protocol statusline integration

I also experience that and this plugins is nice to know what the lsp is doing in the background: https://github.com/nvim-lua/lsp-status.nvim

I use lsp status https://github.com/nvim-lua/lsp-status.nvim