vim-snippets VS vim-fugitive

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

the only reason I do some git stuff in vim and not _always_ in the shell, is because tpope is very thoughtful and fugitive.vim provides nice ways to deal with hunks or hunk partials (visually selecting a range within a hunk, for i.e.)

https://github.com/tpope/vim-fugitive/blob/master/doc/fugiti...

I agree, navigating blame history is incredibly useful, if only to save you from asking the wrong person about a particular change.

Vim's Fugitive[1] can do this and also in Textmate to. So I would hope that most editor git plugins can.

1. https://github.com/tpope/vim-fugitive

Git: vim-fugitive and gitsigns.nvim

You'll want to invest the time in learning Magit, which will change your life once you get the hang of it (and I was a heavy user of Fugitive in Vim previously!), and it's unlikely you'll find a better integration with GDB anywhere else on the planet than with Emacs, though I can't say that empirically. You just need to take the plunge and start learning it, then cut over and take the hit in productivity one day when you're feeling adventurous. You'll ultimately become far more powerful than you've ever been. Especially if you delve into elisp over time. I use Spacemacs, which is bloated and has bugs, but it has so many features that I haven't undertaken the massive endeavor to replace it from scratch yet.

For an option that works on Vim, if you already use tpope's vim-fugitive, there's vim-rhubarb (for GitHub) and fugitive-gitlab.vim (for GitLab).

I replace vim-fugitive with :! git

The only thing I truly miss from Emacs is [Magit](https://magit.vc/) since I still consider it the best git wrapper available. It is just too good. Unfortunately [Neogit](https://github.com/TimUntersberger/neogit) is not quite there yet although I hope it makes it at some point. I didn't like [Fugitive]https://github.com/tpope/vim-fugitive), but I ended up finding a good enough workaround by using [Lazygit](https://github.com/jesseduffield/lazygit) through [Toggleterm](https://github.com/akinsho/toggleterm.nvim).

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

Edit: je viens de trouver [https://github.com/tpope/vim-fugitive de Val