crates.nvim VS rust-tools.nvim

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

FYI: The versions come from the Saecki/crates.nvim plugin.

Hello! I'm trying to break up my existing init.lua file into multiple files according to the existing vim rtp. For example, I'm a rust developer and the crates plugin is extremely helpful for me but it's only ever useful when I'm editing Cargo.toml files. As a result I've put the plugin in pack/plugins/opt/ and I packadd crates.nvim in my init.lua file. This actually works nicely but when I try to factor the config and loading of this plugin into ftplugin/toml.lua it doesn't load despite it indicating that the file was sourced in the output of --startuptime. Curiously if I initialize the plugin in init.lua and then modify the config in ftplugin/toml.lua the updated config is used. So it seems like toml.lua can modify an already loaded plugin but can't load one itself. Is this the case? I'd very much like to relegate all toml related configs to its ftplugin file.

github.com/Saecki/crates.nvim

crates.nvim maybe?

So to fix the shortcomings I felt with vim-crates and to teach myself a bit of lua I created crates.nvim. It sports a nvim-cmp completion source, a popup that list all versions for a crate, live updates while editing and some more stuff that I found to be useful.

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.