fugitive (via vim) VS VisualSVN

fugitive (via vim) mentions (69)

• GitUI

  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. - Source: Hacker News / 4 months ago

• Is it too late to learn emacs as a vim lifer?

  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... Source: 8 months ago

• webify.nvim - Open the current file in the remote's web interface (github or gitlab) or yank its URL

  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). Source: 11 months ago

• Vim users who work without any plugins, how does your vimrc look like?

  I replace vim-fugitive with :! git. Source: 12 months ago

• Switching from Emacs. My experience

  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... Source: 12 months ago

VisualSVN mentions (0)