cmp_luasnip VS paq-nvim

did you installed the plugin cmp_luasnip?

Do you have install the cmp_luasnip plugin for cmp?

cmp_luasnip: Completion source. It shows available snippets in the suggestions.

cmp-luasnip: integração do LuaSnip com nvim-cmp;

Did you also installed cmp-luasnip?

In order for them work you should have these plugins. * nvim-cmp * Luasnip * friendly-snippets (optional) * cmp_luasnip And here's my nvim-cmp configuration for reference.

I created an issue in cmp_luasnip but I'm not even if it's cmp_luasnip or if it's nvim-cmp or LuaSnip.

cmp_luasnip

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