vim-textobj-user VS nvim-treesitter-textobjects

Using lazy, it throws the error 70% of the time. when it doesn't throw the error it works. but It uses a dependency (vim-textobj-user) and I already tested it (only using that plugin without other plugins) is not the dependency's fault.

Just to add to that, there are also various plugins that give you additional text objects, such as: - ii for indent levels (https://github.com/kana/vim-textobj-indent) - iz for folds (https://github.com/kana/vim-textobj-fold) - if for functions (https://github.com/kana/vim-textobj-function) - ic for comments (https://github.com/glts/vim-textobj-comment) - User-defined text objects (https://github.com/kana/vim-textobj-user)

Thank you, kind vimmer. For others stumbling upon this issue, having same character around is not supported in textobj-user, but there's a workaround: https://github.com/kana/vim-textobj-user/issues/48.

The vim-wordmotion plugin extends the idea of words to include snake case and camel case words among other things. On a related note, the vim-textobj-user plugin lets you extend vim's understanding of text objects.

if anyone wants to use this, just make sure to also install https://github.com/kana/vim-textobj-user for it to work

I would highly recommend https://github.com/kana/vim-textobj-user. Specifically, you'd want to pair it with https://github.com/sgur/vim-textobj-parameter. Check the readme for other useful custom text objects, personally I think this is one of my most useful set of plugins

I NEVER use count, because my mental flow is drastically hindered by pausing for any form of counting in midst of editing; I stay off even relative numbers even. In their place, I enable a vast number of text objects instead, quite a few implemented through the `kana/textobj-user plugin`. Good text object are an embodiment of intent and thus map better mentally than any method using brute counting, even at the loss of some precision and speed.

[kana/textobj-user](https://github.com/kana/vim-textobj-user)

I would suggest using vim-textobj-user. Someone has already implemented a path object using this plugin. You can find this implementation here.

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.