vim-signify VS vim-fugitive

Alterntatively, I've been using vim-signify, as we use subversion at work

I wonder why beneath the plus (from vim-signify) the colorscheme is not fully extending to edge of the screen.

That said, Neovim can still run most Vimscript plugins just fine, so you can still use https://github.com/chrisbra/changesPlugin (and https://github.com/airblade/vim-gitgutter and https://github.com/mhinz/vim-signify/, which are mentioned in the README) if you want.

vim-signify or git gutter can do this for files managed by git.

And it happens fairly regularly. This particular error happens in the https://github.com/mhinz/vim-signify plugin, but I would get this same error from different plugins as well.

mhinz/vim-signify highlights the changes similarly to git-gutter

I've given up vim-gitgutter for mhinz/vim-signify because of performance. But vim-gitgutter has this one killer feature for staging the hunk currently under the cursor. This feature doesn't exist elsewhere.

I use :Gdiffsplit from https://github.com/tpope/vim-fugitive which opens a diff window. And I use https://github.com/mhinz/vim-signify to have some info at all time

👉 Vim-Fugitive plugin for git.

Git integration: fugitive

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