vim-mucomplete VS vim-sleuth

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.

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