telescope-fzy-native.nvim
trouble.nvim
telescope-fzy-native.nvim | trouble.nvim | |
---|---|---|
7 | 59 | |
172 | 4,722 | |
0.0% | - | |
0.0 | 7.6 | |
over 1 year ago | 11 days ago | |
Lua | Lua | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
telescope-fzy-native.nvim
-
NVIM v0.9.0-dev + Telescope extremely slow on large codebase - was forced to open VSCode
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.
-
telescope-zf-native.nvim - filename focused fuzzy finding
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.
-
Looking for a neat Neovim config for wilder.nvim
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.
-
speeding up Telescope?
Are you using the fzy-native extension?
-
With the release of Neovim 0.5.0, I felt it's worth asking: How can someone new to neovim start to take full advantage of its features?
Is it faster than telescope-fzy-native (fzY)? Does it provide better results?
-
Trying out telescope.nvim
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
trouble.nvim
-
How to copy LSP diagnostics from folke/trouble to quickfix window?
Does anyone know if it's possible to copy the LSP diagnostics (which currently is being displayed using folke/trouble to the quickfix window?
-
Help with trouble.nvim
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?
-
How can i get better looking errors?
Trouble
-
How do I get neovim to only show LSP errors as underline squiggles and not in the gutter?
Looking at the screenshot here for example https://github.com/folke/trouble.nvim they show errors both in the gutter and underlined.
-
Neovim vs VSCode Neovim - what are the tradeoffs?
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.
-
Is it possible to close todo-comment/trouble's floating window after pressing enter on an item?
I am referring this as well as this this plugin.
-
Video: 5 Neovim Plugins To Improve Your Productivity
Trouble: https://github.com/folke/trouble.nvim
-
People who migrated from vscode
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?
-
Any recommended plugins to frictionlessly see lsp references in a perhaps a popup window?
I like trouble.nvim
-
Disabling PEP diagnostics errors/warnings in LazyVim
I guess LazyVim uses https://github.com/folke/trouble.nvim for it. I should config it to not including errors regarding standardization.
What are some alternatives?
fzf-lua - Improved fzf.vim written in lua
impatient.nvim - Improve startup time for Neovim
telescope-fzf-native.nvim - FZF sorter for telescope written in c
lsp-trouble.nvim - 🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing. [Moved to: https://github.com/folke/trouble.nvim]
denite.nvim - :dragon: Dark powered asynchronous unite all interfaces for Neovim/Vim8
AutoSave.nvim - 🧶 Automatically save your changes in NeoVim [Moved to: https://github.com/Pocco81/auto-save.nvim]
fzy-lua-native - Luajit FFI bindings to FZY
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
nvim-treesitter-refactor - Refactor module for nvim-treesitter
lspsaga.nvim - improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim]
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.