hop.nvim
Our great sponsors
| vim-treesitter | hop.nvim | |
|---|---|---|
| 2 | 4 | |
| 72 | 25 | |
| - | - | |
| 0.0 | 2.0 | |
| over 1 year ago | over 2 years ago | |
| Go | Lua | |
| - | GNU General Public License v3.0 or later |
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.
vim-treesitter
-
Vim Boss – Neovim
You are stating these things as though they were established facts. But they seem to be opinions. Or do you have data to back them up?
> People who are new to vim-style-editors and go to neovim are mainly people who would have gone to vim if neovim didn't exist.
It seems reasonable to assume that a lot of new people would not pick up either Vim or Neovim without LSP integration and Tree-sitter.
Vim has adopted a lot of the early features of Neovim and now Vim9 also has virtual text for rendering LSP diagnostics in the buffer[1] and there is a Vim9 LSP plugin too. But it does not at all seem likely that Vim would have these things were it not for the push from Neovim.
Besides, it looks like Vim still does not have mature support for Tree-sitter.[2]
> Well, the prevalent wisdom of 30+ years of FOSS has been that they're mostly bad.
There are many famous forks from the past 30 years that hardly anybody calls bad. Some examples: Net/Free/OpenBSD, GNU/XEmacs, Open/LibreSSL. These projects allowed people with different goals or values to carry on in their own directions, while also motivating each other to pick up development pace. They have often also shared code with each other.
[1] Which looks like this: https://sr.ht/%7Ewhynothugo/lsp_lines.nvim/
[2] One experimental plugin I came across: https://github.com/mattn/vim-treesitter
-
Bram: "Neovim has included Treesitter, which is an implementation of this. Once Vim9 is done I'll have a look at whether it is a good choice to include with Vim"
mattn might be cooking something: https://github.com/mattn/vim-treesitter
hop.nvim
- There is a fork of hop.nvim that is much better.
- Bram: "Neovim has included Treesitter, which is an implementation of this. Once Vim9 is done I'll have a look at whether it is a good choice to include with Vim"
- Hop around treesitter nodes
-
Custom treesitter textobjects
- https://github.com/IndianBoy42/hop.nvim : This is my fork of hop.nvim, i got tired of waiting for PR#123 to be merged which refactored hop.nvim to allow for more flexible ways of specifying jump targets (instead of line by line you return everything visible on the screen). This allowed me to write some extensions that use treesitter to jump to locals, like definitions, references, scopes, and any other queries you want
What are some alternatives?
nvim-treehopper - Region selection with hints on the AST nodes of a document powered by treesitter
nvim-treesitter-textsubjects - Location and syntax aware text objects which *do what you mean*
iswap.nvim - Interactively select and swap function arguments, list elements, and much more. Powered by tree-sitter.
nvim-treesitter-context - Show code context
nvim-gps - Simple statusline component that shows what scope you are working inside
Vim - The official Vim repository
treesitter-unit - A Neovim plugin to deal with treesitter units
vim-treesitter - vim async coloring experiment
ts-textobjects - Treesitter textobjects for neovim.