paq-nvim VS vim-packager

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

I use https://github.com/kristijanhusak/vim-packager

my plugin manager config is in a file called manager.vim in my plugin directory, my manager being vim-packager and located in pack/packager/opt directory. All I want is to have this manager.vim file, when needed do a packadd vim-packager do whatever I need in my manager file lunch Packager{Install,Update,Clear} and that's all. But for now when I do a packadd vim-packager and I any of these commands Vim tells me E492: Commande inconnue: PackagerInstall. How can I manage that ?

vim-packager