crates.nvim VS paq-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.

If you want a dead simple package mamage that only puts packages in opt and start, you can use paq.nvim

Is there anyone here who can share some feedback on how much lazy.nvim has been better than what you were using previously? If my context helps, I'm using paq-nvim, previously was using packer.

This was a problem when I was using paq as my manager, now I have the same problem with packer. It never happened when I wanted to install new plugins, only on updating. With packer I have a workaround: after it fails to sync it allows to re-run all failed jobs, and each times about a half of failed jobs fail again, others update successfully, so I can iteratively sync everything, but that's a terrible waste of time;

Options: - packloadall command family and maybe git submodules - minpac which is a thin utility around the above - vim-plug - old but still popular for it does the job - packer.nvim is a popular choice for lua configs, never got to using it myself - paq-nvim is another often mentioned lua solution - dozens of other solutions

that sounds like paq, but slow?

On my Neovim setup, I simply have the following plugins. I use paq as a plugin manager:

paq.nvim