bob VS telescope-fzy-native.nvim

That depends on the debian stable repo what version of Neovim they provide. My suggestion would be to check out bob, which as far as I'm concerned it's the easiest way of installing Neovim and gives you the ability to switch between stable and nightly.

Config details: 0. Distribution: AlmaLinux 9 (what I'm forced to use at work) 1. Also requires: git, curl, clang, rustup, fzf 2. neovim version manager: https://github.com/MordechaiHadad/bob 3. I'd like to use the LazyVim setup 4. using an nvims() shell function to switch between setups (default & LazyVim, for now) (see https://gist.github.com/elijahmanor/b279553c0132bfad7eae23e34ceb593b)

Auto-install of Bob Neovim version manager (optional)

I personally use bob, ($ cargo install bob-nvim), and it's been great for ease of version management, including nightly

Honest just use bob on non-bleeding edge distro

There's already bob (Version manager for Neovim)

I use on all platforms: https://github.com/MordechaiHadad/bob

current stable is 0.8.3 maybe try the unstable ppa or appimage or bob.nvim

If you want to peek at it now, you could try a neovim version manager like bob... https://github.com/MordechaiHadad/bob I've been using it recently and it makes experimenting with new stuff a bit easier. Then if you run into issues you can switch back to a stable release. I'm considering doing a video on this too since I think it would be helpful to some... and I don't think it's very well known

I recommend the fzy native extension for telescope. https://github.com/nvim-telescope/telescope-fzy-native.nvim it’s still not quite as fast as the old fzf solution but I don’t notice it unless I’m working on some huge legacy codebase.

This plugin provides precompiled libzf libraries packaged into a sorter for Telescope, similar to telescope-fzf-native.nvim and telescope-fzy-native.nvim. This gives the speed improvement of native code, and the benefits of the zf algorithm inside telescope for all pickers.

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.

Are you using the fzy-native extension?

Is it faster than telescope-fzy-native (fzY)? Does it provide better results?

I want to give a little update on the speed problem, since this is coming up more or less on every Telescope thread. Having bugged the developers opening regular GitHub issues, it seems that you can get a consistent jump on search speed by using the native sorter