paq-nvim VS telescope.nvim

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

for telescope.nvim (optional) live grep: ripgrep find files: fd

Here we have a configuration for telescope.nvim, a very popular fuzzy finder.

EDIT: I found what I was looking for https://github.com/nvim-telescope/telescope.nvim and https://github.com/nvim-telescope/telescope-file-browser.nvim

Fuzzy Finder: fzf.vim (for its speed) along with telescope.nvim (for its ecosystem)

Just landed on Telescope.nvim: https://github.com/nvim-telescope/telescope.nvim/pull/2572

This extension allows you to use the power of ast-grep to find code patterns in your editor, using the familiar and awesome interface of telescope.nvim.

telescope.nvim

My solution is using telescope.nvim with lsp extension, and map the vim.lsp.buf.definition keybinding to telescope one https://github.com/nvim-telescope/telescope.nvim