nvim-treesitter-textobjects VS targets.vim

I was hoping to use nvim-treesitter-textobjects to jump to the next argument via something like this:

You want to look at nvim-treesitter-textobjects. It let's you define keymaps for navigating text objects defined by treesitter and you can also use them with commands like d, c and so on.

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

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

I'm aware of nvim-treesitter-textobjects and I suspect my answer lies in this plugin, but is there a way to move between root nodes that is agnostic of the node type?

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

nvim-treesitter-textobjects

In this case, reading here is probably a good start: https://github.com/nvim-treesitter/nvim-treesitter-textobjects

Have a look at https://github.com/nvim-treesitter/nvim-treesitter-textobjects. Set up the @block.inner and @block.outer textobjects and it should work.

nvim-treesitter-textobjects lets you jump to (for instance) functions more accurately than with a regex-based approach using ]f

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

targets is nice too.

The thing that has the biggest impact on me is ci”, ca”, da”, etc.. so I suggested getting used to using those.. and then you can get more pedantic with it using https://github.com/wellle/targets.vim

I do recommend getting, targets.vim https://github.com/wellle/targets.vim .. which unlocks the n(ext) and l(ast) verbs(?) ..ahhhh it’s REALLY REALLY good, I use 2in” like a lot

In fact, as /u/Chillbrosaurus_Rex points out, there's a plugin, targets.vim, that expands on Vim's built-in text objects, and one of the things it does is to provide this kind of forward and reverse direction functionality.

Hey, I use targets.vim, how does it compare with that?

You might benefit from targets.vim, it works well with your thought process. It adds a bunch of new really useful editing targets (which should be builtin imo).

https://github.com/wellle/targets.vim

Thanks for the through explanation. I has seen that and considered using it in the past. Can I ask how it compares to https://github.com/wellle/targets.vim? Would you consider mini.ai a replacement or complementary?

This is provided by targets.vim, along with a bunch of other useful text objects.