.cfg VS targets.vim

Internal validation behaviours are a bit complex to be fully described in this article. The full code is found here, though.

It is possible to find related configuration files tracked in my dotfiles repository. Also, I gathered the most helpful resources I found in the Neovim learning path. You will find at that location most of the resources I am going to reference, and also additional ones I could not fit in this article.

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.