nvim-autopairs VS targets.vim

I would like to be able to jump out of a pair generated by nvim-autopairs (https://github.com/windwp/nvim-autopairs) using a Tab. To me it is impossible to get out of the habit of using tab for it, as placing an autopair looks and feel like a snippet, and I typically move out of a snippet with a tab.

A couple nice quality of life plugins would be: Comment (which lets you use a keybinding to comment/uncomment things), Autopairs (which will make the paired brackets/parentheses/etc.), and Rainbow2 (which color-matches the pairs if things like parentheses).

abecodes/tabout.nvim windwp/nvim-autopairs

As an example, I give a slight edge to windwp/nvim-autopairs because it can turn 'test' into {'test'} just by pressing { instead of me having to use surround with something like gzaa'{

autopairs has worked for me

I think I have two plugins that affect this -- nvim-autopairs and cmp

For Rust closures, I'd like to have an autopair for "|" -- any idea how to actually add that to the nvim-autopairs plugin? (https://github.com/windwp/nvim-autopairs) This plugin has a lot of fancy stuff I do not need, but I'm not sure how to do this very basic thing.

Having trouble with nvim-autopairs. I'm trying to define a rule for automatically closing $ in .tex files, but I keep getting this error

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.