vim-clap VS plenary.nvim

I'm thrilled to share that the latest vim-clap has now integrated the tree-sitter highlighting into Vim and NeoVim. It's a PoC implementation and not extensively tested though, bugs are expected. Some early feedback is highly appreciated, and read more in this post!

It has been two years since I last posted about the update of vim-clap. A lot of features have been added to vim-clap since then, check out the CHANGELOG if you are interested. Today I want to share with you a feature that I want to support in vim-clap for quite a long time: the search syntax of fzf, which is powerful yet pretty handy in my opinion. Feel free to try #738 and leave some feedback.

Free free to test the PR #738 and leave some feedback.

I'll also take the occasion to recommend clap.vim, which is the picker I use. It's super cool, fast, and uses a rust backend for more intensive searches.

- https://github.com/nvim-telescope/telescope.nvim or https://github.com/liuchengxu/vim-clap for file navigation (I'm still deciding which one I will continue to use)

vim-clap supports filer so I can search for files in different directories outside my project.

(For me) New vimscript fuzzy finder I was unaware about: https://github.com/liuchengxu/vim-clap (the search field is a vim buffer which I loved)

we can create a function to open a pop up menu using plenary.popup like this, you need to install neovim plenary if you don't already have it https://github.com/nvim-lua/plenary.nvim

If you are really interested in doing this yourself with loop, you should take a look at either plenary.job or netman.shell (I made the latter) as both are very well documented.

I feel this :( That said, alot of plugins rely on plenary.nvim. Its up to you if you determine this is "non-essential" or not. It will almost certainly be available for you to use already.

The big reason I ask is that reaching out to an external python shell to run commands (disregard the fact that its python running) is going to be much slower than using the in built lua JIT interpreter. Additionally, plenary has a built in curl function so you don't have to "reinvent the wheel".

There is also test harness in nvim-lua/plenary.nvim with a slightly different design, but still usable of course.

I am simply using busted or more specifically vusted which is a wrapper around busted for Neovim. It should be quite straightforward to learn the basics, I would say you mostly need to know these functions: describe, it (these are used to structure your test cases) and assert.are_same (to check for table equality). Some people are also using plenary which is also based on busted.

It's based on nvim-lua-plugin-template, but uses Nix flakes to run plenary.nvim tests.

Plenary plugin for Nvim