Document opening diff split from patch #2220
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
idbrii
force-pushed
the
doc-diffsplit
branch
2 times, most recently
from
9164ea4 to
0e95f98
Compare
References tpope#2219. There's awesome special behaviour for buffers with diff output to view it in a split diff instead of unified diff.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's awesome special behaviour for buffers with diff output to view it in a split diff instead of unified diff. It wasn't obvious to me: #2219.
Let me know if my terminology needs correcting.
I also thought it was great that I could
set foldmethod=syntax foldlevel=0to collapse diffs down to a list of files that you can pressoto open in a split diff. But that seems excessively detailed for the doc.