-
I love tpope's fugitive.vim plugin so so much and use it every friggin day. Shout out to everybody who writes a proper git commit message that tells me what your intention was while you were working on something. It's truly a dream.
-
…in reply to @jefflembeck
To dive further into this, if I'm new to a large file and I'm reading through it, there will be moments I'm going to go "_Wait why?_" and sometimes I'll go "God I hate this." They're going to happen and the best thing to do at that point, for me, is to type :Git blame
-
…in reply to @jefflembeck
I'm not looking for _who_ wrote this, though that might be useful! If they still work with me, I can probably go ask them why they took a certain approach. Maybe business demands were different then (likely). Maybe somebody was trying to be a clever little script kiddie.
-
…in reply to @jefflembeck
What I _am_ looking for is the commit and the message attached. I can "return" my way into that commit right there and it opens a buffer that shows me the full git commit. Change, message, everything. I can read through, see all of what happened. Hopefully understand. Then :b#
-
…in reply to @jefflembeck
I do this 20x/day when I'm the new guy on a project. It's a godsend.