treesitter-unit VS cmdchallenge

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

~/git/cmdchallenge master ± inotifywait -m --event create,modify,delete . & [1] 110764 Setting up watches. Watches established. ~/git/cmdchallenge master ± git pull remote: Enumerating objects: 768, done. remote: Counting objects: 100% (209/209), done. remote: Compressing objects: 100% (24/24), done. remote: Total 768 (delta 200), reused 185 (delta 185), pack-reused 559 Receiving objects: 100% (768/768), 323.39 KiB | 16.17 MiB/s, done. Resolving deltas: 100% (474/474), completed with 10 local objects. From https://gitlab.com/jarv/cmdchallenge e97638c3..2c059b85 master -> origin/master * [new branch] next -> origin/next * [new branch] renovate/github.com-docker-docker-23.x -> origin/renovate/github.com-docker-docker-23.x * [new branch] renovate/github.com-mattn-go-sqlite3-2.x -> origin/renovate/github.com-mattn-go-sqlite3-2.x Updating e97638c3..2c059b85 ./ DELETE .asdf-plugins ./ CREATE .asdf-plugins ./ MODIFY .asdf-plugins ./ DELETE .envrc.example ./ CREATE .envrc.example ./ MODIFY .envrc.example ./ DELETE .gitignore ./ CREATE .gitignore ./ MODIFY .gitignore ./ DELETE .tool-versions ./ CREATE .tool-versions ./ MODIFY .tool-versions ./ DELETE Makefile ./ CREATE Makefile ./ MODIFY Makefile ./ DELETE README.md ./ CREATE README.md ./ MODIFY README.md ./ DELETE challenges.yaml ./ CREATE challenges.yaml ./ MODIFY challenges.yaml ./ MODIFY challenges.yaml ./ MODIFY challenges.yaml ...

I have written a bit of both, recently re-wrote a command runner for a side-project https://gitlab.com/jarv/cmdchallenge in Nim and found it very pleasant and much less verbose, which was a nice change from GoLang while keeping type safety. A good example is parsing JSON https://nim-by-example.github.io/json/ as you can do a lot with fewer lines of code. I think the main disadvantage of Nim is that there is less out there in the ecosystem, libraries, and it's more likely you will run into quirks and bugs in the standard library.