mini.nvim VS nvim-autopairs

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

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