vim-snippets VS fzf.vim

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).

Like you said, there's ways to do this from within nvim (telescope.nvim and fzf.vim, to name a few), but this doesn't require any setup.

Seems to be fzf.vim and :BCommits

`BCommits` command in fzf.vim

For fzf, there's https://github.com/junegunn/fzf.vim. Also check out :help fuzzy-matching.

I’d recommend FZF and :Buffers https://github.com/junegunn/fzf.vim I have it mapped to p

Personally I'm on neovim these days, but I believe I used fzf when I was vim classic.

Nowadays, I mostly use a fuzzy finder to find the files I want, but a file explorer can still be useful in some situations:

I'm a Neovim and telescope user myself, but AFAIK fzf.vim covers most of the built-in functionality of telescope (if not all of it). But telescope has tons of extensions outside from the built-in ones.

Re: Telescope and fuzzy finder plugins, the big one for vim is https://github.com/junegunn/fzf.vim. So this is a non-issue.