vim-mucomplete VS asyncomplete.vim

If you don't mind using tags instead, a lighter alternative would be to use MUcomplete with the following settings:

You can use the mucomplete plugin, with the following settings:

You can use mucomplete plugin with built-in vim command completion (suggested by @Fantastic_Cow7272) added to completion chain

If you have a LSP client providing an omnicomplete function (such as vim-lsp), you can use mucomplete to enable "completion as you type". That setup is both Vim and Neovim compatible! :)

MUcomplete?

I use the mucomplete plugin, which makes Vim's builtin completions feel more Sublime-like.

Thanks for the suggestion. This set me on the right track - nvim-cmp didn't integrate well with my other plugins, but I found a very similar plugin called vim-mucomplete. Works out of the box and is equally minimal. Can also be configured for compatibility with stuff like UltiSnips.

There are plugins that may improve this experience for you, like supertab, vimcompletesme, or vim-mucomplete. You can find more completion plugins here.

There's a plugin, vim-mucomplete, that is built around combining some of the Ctrl-X bindings with, of which there are many. I used mucomplete to learn what all the various functions do and then uninstalled it, because I found the individual bindings easier to remember.

This is where completion plugins bring some value, like asyncomplete.vim, YCM, nvim-cmp for neovim only, ...etc.

I am using https://github.com/alaviss/nim.nvim alongside https://github.com/prabirshrestha/asyncomplete.vim for Nim development. I am using several other QoL plugins as well, but those don't really touch stuff like that. Maybe treesitter should be named.

asyncomplete

With [vim-lsp](https://github.com/prabirshrestha/vim-lsp) and [asyncomplete.vim](https://github.com/prabirshrestha/asyncomplete.vim) you can get vim to be pretty close to other IDES. I use vim purely for rust and typescript.