denite.nvim
telescope-fzy-native.nvim
| denite.nvim | telescope-fzy-native.nvim | |
|---|---|---|
| 3 | 7 | |
| 2,055 | 172 | |
| - | 0.0% | |
| 4.3 | 0.0 | |
| about 2 months ago | over 1 year ago | |
| Python | Lua | |
| GNU General Public License v3.0 or later | MIT License |
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.
denite.nvim
-
Ask HN: Is switching from VSCode to Vim worth it?
- The buffer, tab, window, model (probably the biggest one I miss when I start using VSCode)
For LSP support, I've tried to migrate to neovim's native LSP tools, but I still find COC to be a lot more intuitive. You should feel right at home with it since a lot of the plugins are similar to their VSCode counterpart.
If you'd like a really general and guided tour of VIM, I'd recommend picking up Practial Vim[2] It really helped me understand the workflow a bit more. Approaching VIM with the mindset of another editor wont give you all the benefits of using VIM. Though, if the workflow doesn't click, then that's not a big deal. You can always go back to VSCode.
[1] https://github.com/Shougo/denite.nvim (many people use Telescope: https://github.com/nvim-telescope/telescope.nvim)
-
Looking for a neat Neovim config for wilder.nvim
cpsm doesn't use ctrlp.vim, it's a matcher initially targeted at ctrlp, but has since been adapted for use in other fuzzy matching plugins, e.g. denite.nvim
-
Converting from an IDE, biggest issue is navigating between files efficiently
Highly recommend Denite. It gives you a graphical way to easily switch between buffers. It's super intuitive and fast.
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
What are some alternatives?
fzf.vim - fzf :heart: vim
fzf-lua - Improved fzf.vim written in lua
vim-projectionist - projectionist.vim: Granular project configuration
telescope-fzf-native.nvim - FZF sorter for telescope written in c
vim-vinegar - vinegar.vim: Combine with netrw to create a delicious salad dressing
fzy-lua-native - Luajit FFI bindings to FZY
vim-autoimport - A vim plugin for adding import statements (for python and more) without LSP
nvim-treesitter-refactor - Refactor module for nvim-treesitter
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
wilder.nvim - A more adventurous wildmenu
vim-clap - :clap: Modern performant fuzzy picker, tree-sitter highlighting, and more, for both Vim and NeoVim