crates.nvim VS crates.nvim

Ha-ha, what a funny coincidence! I've recently started working on plugin with same idea too. Love your approach to make user configurate everything!

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.