nvim-defaults.vim VS paq-nvim

To make it easier, I wrote a plugin so Vim has the similar defaults to neovim. Vim finds .vim files using neovim paths (e.g. ~/.config/nvim/init.vim and ~/.local/share/nvim/site)

This plugin gives Vim the same defaults, path and directory layout as Neovim: https://github.com/mikeslattery/nvim-defaults.vim

I am keeping my config backward compatible with Vim, so I'm only using Lua for neovim-specific stuff. If packer is compelling enough, I may make a break with Vim (and instead use sshfs or nvim scp://... to edit remote server files).

Ever ssh into a server and which you had nvim and its defaults, and/or maybe the ability to use your nvim dotfiles? I wrote a plugin for that: https://github.com/mikeslattery/nvim-defaults.vim

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