hop.nvim VS treesitter-unit

- 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

It's also relatively easy to write plugins based on the parsed AST. I wrote treesitter-unit[1] making it easy to select/modify the subtree of the selection.

[1]: https://github.com/David-Kunz/treesitter-unit

I built a plugin to select units of tree-sitter objects https://github.com/David-Kunz/treesitter-unit

To delete/yank the node, the combination would be `diu`, using this plugin: https://github.com/David-Kunz/treesitter-unit

Hi, I also think treesitter-textobjects are a bit overspecific, that's why I created https://github.com/David-Kunz/treesitter-unit/ .

In this video I create a Neovim plugin called 'treesitter-unit' using Lua. You can find the final plugin here: https://github.com/David-Kunz/treesitter-unit/

I tried it with operator mode maps and it works perfectly! I updated the README to include: vim.api.nvim_set_keymap('o', 'x', ':lua require"treesitter-unit".select()', {noremap=true})