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
In all current versions, when the cursor is over a diff belonging to a deleted file, i.e. where git shows
--- a/foo.c +++ /dev/null
the window statusbar shows [diff] Changes to '/dev/null' and pressing f attempts to open /dev/null as a blob.
[diff] Changes to '/dev/null'
Would it be possible for view-blob to show the old file in this situation, even though it normally shows the new file?
view-blob
The text was updated successfully, but these errors were encountered:
Yes, we could use the same logic as when opening the blame view from the diff view to identify the blob corresponding to the diff line.
Sorry, something went wrong.
Open the blob corresponding to the diff line
c0fee6a
Fixes jonas#1334
935fdba
2a8ef0f
No branches or pull requests
In all current versions, when the cursor is over a diff belonging to a deleted file, i.e. where git shows
the window statusbar shows
[diff] Changes to '/dev/null'
and pressing f attempts to open /dev/null as a blob.Would it be possible for
view-blob
to show the old file in this situation, even though it normally shows the new file?The text was updated successfully, but these errors were encountered: