pear-tree VS nvim-compe

After some digging, it turned out the problem was caused by the plugin tmsvg/pear-tree. The solution outlined here worked for me.

https://github.com/tmsvg/pear-tree (the one I use)

In general, having an LSP update the document at unexpected times is problematic for me (especially when the document being checked at random times leads to big flickers of temporary syntax error worse than what I installed pear-tree to reduce from typing things like quotes).

tmsvg/pear-tree for an extensible autocloser (I hate closing GHC {-# LANGUAGE ... #-} myself, and it's not built into any of the common plugins AFAIK)

Most pair matching plugins will let you type the closing brackets explicitly, and skip over them if they're already there. For instance, in pear-tree you'll want to enable Smart Pairing. So that's the easiest answer to your question. If your current plugin doesn't support that sort of behavior, I'd suggest finding one that does; it makes things so much nicer!

Myself, I have been and continue to be a pear-tree user. Works reasonably well, but it does seem to be an abandoned plugin these days. Though I do like that pear-tree has tag pairing support in addition to traditional bracket pairing.

I know this is not the answer you're looking for, but I have tried a lot of auto pairs like plugins and I always have had problems with any of them. This week tried Lexima instead of https://github.com/tmsvg/pear-tree, and I must admit that Lexima is pretty cool. You could try with Lexima and see if it fits your needs.

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 )