Replies: 1 comment
-
Have look at this output, from the source to Git itself:
That ellipsis is concealing part of the file path. It is not possible to reliably get the file name. We could do it 99% of the time, but even settling for that, you're going to run into other challenges. How do you reliably determine what |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello again,
I have searched the documentation, either with the wrong terms, but so far not turned up anything. So would appreciate some guidance!
The scenario I am working with is as follows. For various reasons (one of which being a workaround for #2214) I want to browse the output of
git diff --stat $commit
. That is I want to explore the diff between the current working tree and$commit
, drilling in by opening each file in the stat output and viewing the file diff with respect to$commit
.It feels like the way I want to navigate such a diff is by starting at the
git diff --stat
output. That is have a window that contains something like this:I would then like to be able to put the cursor on the filename in the diff, hit a keyboard shortcut and have that shortcut:
:Gdiff $commit
Am I holding things correctly here?
Is this in the spirit of what fugitive would look to support?
If it is, what's best way of achieving such a "browser" in Vim with fugitive?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions