fzy-lua-native VS plenary.nvim

I don't think it would be a good idea to integrate with telescope, I don't like the design of that plugin too much. Kirby's filtering backend uses fzy-lua-native, which is faster than out-of-the-box telescope. That backend was originally wrote for telescrope tbh (& vim-clap), but they never made it the default so AFAIK they still use lua filtering for basic cases.

It uses fzy-lua-native for filtering, another of my creations in need of love. It filters on the main thread but should be responsive for repos up to maybe a few thousand files.

fzy-lua-native similary doesn't use fzy, it's a matcher based on the algorithm that fzy uses. This is actually the same matcher used under the hood in telescope-fzy-native.

They really should make that extension the default. Besides, the backing fzy bindings also include a lua fallback, it would be much nicer for users to not have to mess around with tons of options to get a fast by default picker. (Disclaimer: I'm the author of the backing fzy bindings)

Anyway, if you're interested in doing the switch open an issue we can discuss further, but otherwise it's not a big deal.

I saw that you're spawning a new job for sorting things. If you're interested, fzy-lua-native is the standalone fzy lua bindings that telescope.nvim and other projects use. It comes with pre-compiled binaries for common OSes (included as-is, no install step needed; but just make otherwise), and fallbacks to a lua fzy implementation in case the binary fails to load.

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