telescope-fzy-native.nvim VS trouble.nvim

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

Does anyone know if it's possible to copy the LSP diagnostics (which currently is being displayed using folke/trouble to the quickfix window?

A newbie here, I used jose-elias-alvarez/null-ls.nivm for diagnostics and formatting, but I recently discovered folke/trouble.nvim and for me, it seems like a better option However, I don't know if it supports formatting and linting, I don't even know if it is an alternative to null-ls. So I need your help, can trouble.nvim replace null-ls? If not, can I use both of them simultaneously?

Trouble

Looking at the screenshot here for example https://github.com/folke/trouble.nvim they show errors both in the gutter and underlined.

All you need is just the LSP working (with linter, formatter and diagnostics) and telescope. Seriously, telescope is the GOAT, way faster than a file tree, you end up using the filetree only to move, create and delete files/folders but if it's just for that, you might as well use the terminal instead. For the LSP, it's not only autocompletion and hints at hover but formatting and diagnostics. I use lsp-zero + null-ls + trouble. I exposed all of the keybindings on those so I can at least open my own configs for guidance. Oh yeah, having treesitter is probably a must too, and it has no keybindings on its base form.

I am referring this as well as this this plugin.

Trouble: https://github.com/folke/trouble.nvim

Trouble is so good for finding errors easily. For testing I use jest so I haven't had too many issues. What do you test with?

I like trouble.nvim

I guess LazyVim uses https://github.com/folke/trouble.nvim for it. I should config it to not including errors regarding standardization.