vim-snippets VS vim-mucomplete

Also, I'm using vim-snipmate style snippets in LuaSnip. How can I import snippets in javascript.snippets in html.snippetswithout having to copy everything.

cmp works fine and I was able to trivially make it only suggest lsp completion for me by only including lsp sources. The setup is significantly more complicated with having the install 7ish plugins instead of just 3 for coq. I don't think I would've had the patient to go through the setup when I was just starting to use neovim. cmp also have much nicer UI (e.g. it shoulds documentation and sometimes function signiture as you browse through the suggestion.) With snippet you can find something like https://github.com/honza/vim-snippets which have more than what I need. You also need to choose a snippet engine so that's more decision to make.

Since LuaSnip also supports snipmate I'm using vim-snippets since it's offering a lot of snippets I'm using often without having to write my own. But as @eliizaak said: it's not Lua and perhaps I'll find the time and energy to learn a bit more about LuaSnip and write my own snippets ... ;)

Does this include snippets apart from honza/vim-snippets?

It includes the snippets from honza/vim-snippets and my own snippets.

vim-snippets as you've already mentioned.

Skimming over the blog post you linked, it appears that the author uses Vim plugins to get some of the snippets working, which I'm near-certain is impossible with the Vim features available to Obsidian. I don't think installing Vim plugins with vim-plug (as used by both myself and the author of the linked blog) is possible in Obsidian, for example. Without some way to manage installing Vim plugins, you won't be able to get plugins which enable vim snippets as used in the blog post.

Sorry does it?

Auto adding include files or a specific non-static function is generally a bad idea, but I use yasnippet on Emacs for copyright/licensing info, this seemingly has the same purpose but oriented towards vim users, which makes file templates trivial (on Emacs at least, I don’t usually use vim unless I can’t use Emacs or mg for some reason).

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! :)

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.

I think the best solution to get snippets working with native completion would be something like MUcomplete, which can integrate with a bunch of snippet plugins. I personally prefer to keep control over what kind of completion I see, but MUcomplete is quite good.

mucomplete

diff --git a/.vimrc b/.vimrc index 7f727b8..65a4c7a 100644 -------- a/.vimrc +++ b/.vimrc @@ -148,6 +148,7 @@ silent function! WINDOWS() endfunction set omnifunc=syntaxcomplete#Complete +set spell " Smart mapping for tab completion " https://vim.fandom.com/wiki/Smart_mapping_for_tab_completion @@ -172,4 +173,4 @@ function! Smart_TabComplete() endif endfunction -inoremap =Smart_TabComplete() +" inoremap =Smart_TabComplete() diff --git a/bin/plugins.sh b/bin/plugins.sh old mode 100644 new mode 100755 index 23d88c2..ab903ec -------- a/bin/plugins.sh +++ b/bin/plugins.sh @@ -6,4 +6,15 @@ fi cd ~/.vim/pack/bundle/start -git clone --depth 1 https://github.com/lifepillar/vim-mucomplete.git +git_plugins=( "tpope/vim-sensible" "lifepillar/vim-mucomplete" "tpope/vim-fugitive" "tpope/vim-commentary" "tpope/vim-surround" "tpope/vim-vinegar" "tpope/vim-sleuth" "tpope/vim-obsession" "raimondi/delimitmate" "ctrlpvim/ctrlp.vim" ) + +for plugin in "${git_plugins[@]}"; do + folder=$(echo $plugin | cut -d'/' -f2) + if [ ! -d "$folder" ]; then + git clone --depth 1 "https://github.com/$plugin.git" + else + cd "$folder" + git fetch origin + cd .. + fi +done

mucomplete is similar, and looks like it offers a bit more control at the cost of complexity.