nvim-autopairs VS lspsaga.nvim

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

Just like this? If yes, you can try lspsaga.nvim, nvim-navic, or barbecue.nvim.

I am not 100% sure if that is what he is using but you can achieve the same thing using Lspsaga, specifically the on_insert and on_insert_follow options

Participating — I'd like to see more contributors for LSP Saga, the various ChatGPT plugins, and pets!

Maybe Lspsaga could help

I think the LspSaga plugin has a hover_doc function! it's been really useful for me :D

Yo, good question.. Yes i have. It's actually working now i filed an issue on lspsaga and the owner created a quick fix for it: https://github.com/glepnir/lspsaga.nvim/issues/866

You might like this: https://github.com/glepnir/lspsaga.nvim.

I already did, but you closed it 🫡 here is the link

Did you post an issue on GitHub? The library author has been exceptionally quick to respond to bugs and reports like this in my experience.