vim-surround VS vim-snippets

I don't know what exactly you mean by pasting around the second selection, but you can paste selections, registers or even files at specific lines with some vim-fu. If it's generic enough you could write a function or even keyboard shortcut if it's very simple.

I have set ",',(,[,{ in visual mode to cut the selection insert the pairs then paste it back as a very hacky solution, but it gets the job done. If you want something more advanced to add or change anything around the selection tpope has solved that with vim-surround[1].

[1]: https://github.com/tpope/vim-surround

ysw https://github.com/tpope/vim-surround basically i surround the word with " So basically i wanted to surround the first word in line qoutes and then replace the first occurence of = with : Example:

vim-surround is likely the plugin answer.

If you have Tim Pope's vim-surround plugin, you can also add this to your Vimrc:

If you don't want to leverage Vim's package feature or you want to put your plugins in some other place, add the folder of the plugin to your :h 'runtimepath'. For example, if you download Tim Pope's vim-surround at ~\Documents\vim-surround, you should add this to your Vim configuration:

I'm using the vim-surround plugin by tPope and I know I can do ysw to surround words with whatever tag i want, I also know about cst (Change surrounding tag). But I'm wondering if there is a quick and easy way to wrap components. Some components might have closing tag and some components might not.

Is there any similar plugin to https://github.com/tpope/vim-surround?

Vim plugins (without UI) work out of the box. Hello vim-surround, argtextobj.vim and whatnot.

If you don't insist on staying in insert mode then you can use vim-surround, which is perfect for this: yse

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