15 ms·
This article glosses over what I consider to be the killer workflow of Fugitive. Specifically the ability to trace history extremely efficiently across any kin
by dasil003 1y ago
This article glosses over what I consider to be the killer workflow of Fugitive. Specifically the ability to trace history extremely efficiently across any kind of refactoring.
The flow is:
1. :G blame to blame the current file in a locked split
2. navigate to a line, then hit o to open the commit in another split
3. search for a change of interest, then navigate to either the --- or +++ line and hit o to open the before or after version of the file in another split
4. repeat steps 1-3 as needed to drill to whatever history you need
5. ctrl-w o to kill all the splits and leave you with just the buffer of interest
whereas I'm pretty happy with git CLI for the majority of git interaction, and a graphical client like gitk for visualizing branch history, I haven't found any other history inspection technique or tool that comes close to this.