Oops, of course Blame is only for that file
dblume

dblume commited on 2023-12-17 11:09:53
Showing 1 changed files, with 7 additions and 5 deletions.

... ...
@@ -31,9 +31,11 @@ Install into Vim's built-in package support:
31 31
 ## Common Use Example
32 32
 
33 33
 Say you're on "index.html", and you need to know why a section looks the way
34
-it does. Run `:Blame` to see a list of the commits that _affect only that file_.
35
-The Blame buffer opens at the same position you were at so you don't lose any
36
-context.
34
+it does. Run `:Blame` to see a buffer of "git blame" open at the same line
35
+where you are so you don't lose any context.
36
+
37
+Or run `:Log` to see a list of only the commits that _affect that file_. This
38
+is nice in a repo of thousands of commits, but only dozens are to this file.
37 39
 
38 40
 If you see a commit of interest, move the cursor over it, and type  `:Diff` to
39 41
 see what changes were made by that commit, or `:Show` to see the full commit
... ...
@@ -59,8 +61,8 @@ its commit history.
59 61
 ### :Blame
60 62
 
61 63
 When you're on a regular file or a `:ShowFile` buffer, opens up a `git blame` 
62
-buffer in a new tab that _affect only the file at that commit_, and positions
63
-the cursor at the same relative spot in the Blame buffer.
64
+buffer in a new tab and positions the cursor at the same relative spot in the
65
+Blame buffer.
64 66
 
65 67
 Example, run Blame on a `:ShowFile` buffer named "git show 1234abcd:README.md",
66 68
 and you get a `:Blame` buffer named "git blame 1234abcd -- README.md".
67 69