nvim-autopairs VS nvim-compe

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

I use https://github.com/hrsh7th/nvim-compe and https://github.com/simrat39/rust-tools.nvim along with the built in LSP and auto completion works really well. You will want treesitter and all that setup too.

I want to share my code for my migration from nvim-compe (deprecated) to nvim-cmp. Though, I would describe myself as an experienced Vimmer I am not very familiar with the whole Lua thing (although I really appreciate it and hope that Lua's first class citizen can compete with the elisp ecosystem^^).

Wrong, plain and simple. A total misconception.

compe.nvim

For autocomplete/intellisense: https://github.com/hrsh7th/nvim-compe

But nvim-compe already exists.

completion-nvim OR nvim-compe

Here's some setup idea: - packer for package manager - clangd language server - nvim-lspconfig, required for navigator.lua - navigator.lua for enchanced IDE experience. This is a like adding a sugar to coffee. - completion-nvim OR nvim-compe for enchanching autocomplete & dropdown menu suggestion. - nvim-treesitter for better syntax highlighting. - telescope.nvim for amazing extensible & configurable fuzzy finder, you can also use fzf if you want. - Any custom color scheme you want (preferably one that supports tree sitter, like aurora )