vim-snippets VS obsidian-vimrc-support

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

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

with vim mode enabled in settings, from normal view you can create a new line below with 'o' or a new line above with 'shift+o'. you can rebind with the vimrc plugin.

Another thing I was considering was using this: https://github.com/esm7/obsidian-vimrc-support

The vimrc-support plug-in comes with a built-in surround command which you can bind to.

The one thing that immediately comes to my mind is that you need an extension in order to be able to use a .vimrc. I also don't think you can use any vim plugins.

The plugin esm7/obsidian-vimrc-support and the built-in vim support is the closest we can get for a mouse-free experience.

" .obsidian.vimrc " " A small .vimrc for Obsidian vim bindings " " To enable this file, you must install the Vimrc Support plugin for Obsidian: " https://github.com/esm7/obsidian-vimrc-support " _________________________________________________________________________ " ; (semicolon) - same as : (colon) nmap ; : " (space) - same as : (colon) nmap : " j and k navigate visual lines rather than logical ones nmap j gj nmap k gk

You can extend the built in features with your own config using this plugin: https://github.com/esm7/obsidian-vimrc-support

Obsidian's Vim functionality is just using whatever is available to the codemirror editor, it doesn't actually have all of the features of Vim. It's possible to get a plugin which allows for loading a .vimrc but again, the supported functionality is limited (i.e. there are lots of vim settings and features that do not work despite being valid in a regular .vimrc). It's not hard to find an example of this either; in actual Vim the movement dj will delete the current line and also the line below it. In Obsidian with Vim features enabled, it will only delete the current line. This is a simple example that has nothing to do with getting snippets working, but it is indicative that the actual Vim text editor and the Vim features available to Obsidian are not the same.