treesitter-unit VS nv-ide

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

Booom! Just installed in my nv-ide.

Amazing! just added my nv-ide

Thanks I will give a try in my nv-ide. It can coexist with tpope/vim-rails?

Full stack ruby on rails, here my conf nv-ide

I found a script on Reddit from user u/GustavoKatel and I adapted it to my workflow scratches

Hi migrated my conf , thanks Folke

However here my conf

SSame situation with my configuration. Objectively, the times that something breaks are relatively low and still notified on the plugin repository or via notification and displayed by noice

Thanks, I am trying it with my configuration and using Rails. Works like a charm