nvim-autopairs VS vim-sleuth

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

In addition to setting tabstop and shiftwidth, you might also like this plugin: https://github.com/tpope/vim-sleuth

vim-sleuth auto detects tab size so...

Just add https://github.com/tpope/vim-sleuth and never worry about it again.

At the end of the day I don't really care which a project goes with, I've always just used vim-sleuth to automatically set my tab key to input whatever the current file's indentation is.

VsCode has an internal function from auto-detecting indentation, while my config uses vim-sleuth with indent-blankline.nvim.

If you work a lot on legacy codebases, https://github.com/tpope/vim-sleuth is probably more what you need than editorconfig, as it will work even when one is not present.

The primary advantage of using it is that it has built in heuristics for detecting line wrapping when opening a file (with some Treesitter magic for Markdown to make it more accurate), and also allows for manual swapping between wrapping types. You can think of it as the wrapping equivalent to vim-sleuth.

I just found about Tim Pope's sleuth: https://github.com/tpope/vim-sleuth It supports editorconfig but it also seems to have just better heuristics when an editorconfig file isn't present, so I just decided to replace `editorconfig-vim` with it.

Another solution is try sleuth.vim, that sets automatically your indentation based on the project, buffer and editorconfig