nvim-treehopper VS treesitter-unit

I am trying to set up nvim-treehopper and duplicating the suggested keymaps in a lua config.

Take a look at nvim-treehopper (https://github.com/mfussenegger/nvim-treehopper), a tree-sitter based plugin that lets you select regions of code

This copies the idea of nvim-treehopper. Just a work in progress hack (pretty usable though), but planning to make a full-fledged plugin, if someone else won't do it :) (Needless to say, my gists can be considered unlicensed, do whatever you want with them.)

I also suggest taking a look at this one : mfussenegger/nvim-treehopper

https://github.com/mfussenegger/nvim-ts-hint-textobject does what you are proposing.

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})