syntax-tree-surfer VS nvim-treesitter-textobjects

Your config, tree-surfer or nvim-treesitter-textobjects follow nodes using the syntax tree. Go to parent / child / next siblings ect....

Cool stuff. It might be worth adding this one to a comparison/alternatives list: https://github.com/ziontee113/syntax-tree-surfer

The closest to "treesitter-powered jumps" plugin I know is ziontee113/syntax-tree-surfer. Don't use it personally, but video demos look cool.

treesitter / neovim:

different code block indicators styles : https://github.com/lukas-reineke/indent-blankline.nvim#with-...

collapse / expand / navigate between code blocks : https://github.com/stevearc/aerial.nvim

not exactly colorize, but can customize to just show iteration / loop processes : https://github.com/ziontee113/syntax-tree-surfer

I personally use it for an outline window for my code (aerial.nvim) and quick-selecting code blocks (nvim-treesitter-textsubjects). I've also seen but not used syntax-tree-surfer for code navigation/manipulation and refactoring.nvim for performing refactoring operations. You could also check out awesome-neovim and ctrl-f for "treesitter", though there are many other plugins out there either not on that list or that don't explicitly mention treesitter in their description.

I published syntax-tree-surfer a while ago didn't know that anyone will be interested to use it. Turns out people do enjoy what I do. When I was in school I didn't feel like I mattered to other people. Now I feel like I do, there are people out there that cares about me, giving me help, advices, etc.. It's just really amazing!

I admit, the functionality is blatantly similar to syntax-tree-surfer, but tree-climber should work also in files with comments as well (unfortunately, I could not make syntax-tree-surfer work in my neovim setup at all).

You can use syntax-tree-surfer to select the parent.

Thank you! It looks like nvim-treesitter-textobjects is a good plugin to start with:

https://github.com/nvim-treesitter/nvim-treesitter-textobjec...

Thanks! I just started using https://github.com/nvim-treesitter/nvim-treesitter-textobjects, and it works as a charm.

nvim-treesitter-textobjects

Or even better, one can use nvim-treesitter-textobjects. It already provides function/class selection and go-to functionality out-of-the-box.

You could look into treesitter-textobjects and treesitter-textsubjects: they define "smarter" blocks and function boundaries that work relatively well with python and non-parentheses code.

These are the problem. I have no issue with vanilla vim inside/around motions with nnoremap mi vi, but I can't use all extra inside/around motion plugins like mini.ai and nvim-treesitter-textobjects.

Your config, tree-surfer or nvim-treesitter-textobjects follow nodes using the syntax tree. Go to parent / child / next siblings ect....

I recently wrote a few tests here and it works with github actions as well.

There is nvim-treesitter/nvim-treesitter-textobjects. It serves double purpose: defines per-language queries for which tree-sitter nodes should be considered a function, class, etc. and defines textobjects.