6
User
Recs.
Recs.
7
Updates
Last
Updated
Updated
Activity
19 Options
Specs
Specs are quantitative aspects of the option such as the price
Pros
Pro Seamlessly "Dive into Diffs" to trace the origin & intent of code
git blame
only shows the last change (e.g. a variable rename), but how do you find the origin of the code?
:GBlame
to open blame windowo
on the relevant line to "git show
" the commit- select a diff line from a previous version of the file, and hit
o
to open it- repeat 1 - 3, jumping back through history to find the origin of the line
Pro Quick to see who changed what, and delve into a specific line-change
Using git blame is as easy as :Gblame
, and does the same thing, but should you need some more context, it's quite easy to see the entire commit that introduced the change. No need to copy-paste hashes, just hit enter.
Know any positive aspects of this option?
Cons
Know any negative aspects of this option?
Recommendations
fugitive (via vim)
Recommended 6 years ago
I prefer using the CLI for all my git stuff, but if I don't want to drop into a shell, or background my editor (e.g. resolving complex merge conflicts), I sometimes use this plugin. All the power of your favourite editor, with all the functionality you expect from a git client.
Pro
Great visualization and interactive workflowPro
Uninterrupted workflow for common tasksPro
Seamlessly "Dive into Diffs" to trace the origin & intent of codePro
Quick to see who changed what, and delve into a specific line-changeCon
Yes, it's a vim pluginfugitive (via vim)
Recommended 4 years ago
PhilosophicalParjanya hasn’t added their experience, pros or cons to their recommendation.
fugitive (via vim)
Recommended 5 years ago
ConvivialIshara hasn’t added their experience, pros or cons to their recommendation.