We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I'm browsing commits, how can I switch from a unified diff (opening the commit in a buffer) to a split diff (Gdiffsplit)?
Since a commit can span multiple files, it'd have to act on the file owning the diff hunks under the cursor.
I can CR on a + line to open the file after the change and :Gdiffsplit !^ to start the diff. Not sure how to do that on - lines.
CR
:Gdiffsplit !^
One of my first guesses was to call :Gdiffsplit in the buffer, but that has no effect.
:Gdiffsplit
The text was updated successfully, but these errors were encountered:
I figured out that the line containing the diff command is a special kind of fugitive-object:
diff --git a/data/scripts/file.lua b/data/scripts/file.lua
You can CR or most of the other :help fugitive-navigation-maps keys on that line to open a split diff.
:help fugitive-navigation-maps
I don't think this is anywhere in the help, so I'll open a PR to add.
Sorry, something went wrong.
Document opening diff split from patch
bdca58c
References tpope#2219. There's awesome special behaviour for buffers with diff output to view it in a split diff instead of unified diff.
0e95f98
No branches or pull requests
When I'm browsing commits, how can I switch from a unified diff (opening the commit in a buffer) to a split diff (Gdiffsplit)?
Since a commit can span multiple files, it'd have to act on the file owning the diff hunks under the cursor.
I can
CR
on a + line to open the file after the change and:Gdiffsplit !^
to start the diff. Not sure how to do that on - lines.One of my first guesses was to call
:Gdiffsplit
in the buffer, but that has no effect.The text was updated successfully, but these errors were encountered: