vim-numbertoggle VS paq-nvim

This cool plugin toggles relative numbers on and off in sensible ways: https://github.com/jeffkreeftmeijer/vim-numbertoggle

I use relative numbers with this small plugin: vim-numbertoggle.

vim.api.nvim_command([[ augroup line_numbers autocmd! autocmd TermEnter * setlocal nonu nornu " https://github.com/jeffkreeftmeijer/vim-numbertoggle autocmd BufEnter,FocusGained,WinEnter * if &nu | set rnu | endif autocmd BufLeave,FocusLost,WinLeave * if &nu | set nornu | endif augroup END ]])

That first sentence doesn't make sense because I ended up changing the code and forgot to remove the sentence (lol) (it'll make sense if you check out https://github.com/jeffkreeftmeijer/vim-numbertoggle)

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