syntax-tree-surfer VS mini.nvim

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

Plugin: https://github.com/ziontee113/syntax-tree-surfer

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

This is essentially a tagline of mini.move.

Just as the others suggested, oil.nvim solves this outta the box. I freaking love it (here my config in case ya need it). Apparently also mini.files handles this by default

You mean backwards seeking text objects? You can get those with mini.ai https://github.com/echasnovski/mini.nvim/blob/main/readmes/mini-ai.md

I would like to offer you to join me in saying late greetings to this autumn with a release of mini.nvim version 0.10.0. It is mostly about introducing three (quite feature full, dare I say) modules and minor updates of existing ones.

Last night I cleaned up all the dead code in my config and realised that mini.nvim has to be the single best plugin that I've used. I have a couple of other favourites but this collection has been so consistently good that I wanted to give some thanks to the juggernaut that is u/echasnovski! Thanks for all the work you plugin authors and core maintainers put in to make this editor what it is <3

For example: I spent a lot of time configuring file tree plugins to have the same sorting as VS Code, tweaking their icons, etc. But then I realized I barely used the file explorer at all, and now I'm super happy with the minimal approach of mini.files. I had similar experiences with other plugins that were just adding "fluff" instead of the functionality I was looking for.

Around two weeks ago I've announced the release of mini.files - a file explorer module of mini.nvim with column view navigation and "edit text to manipulate file system" design. This resulted into a great feedback from the community, much of which turned into new features.

A mini.ai textobject specification that you can use standalone