Make blamer process asynchronous #9
Open
Conversation
This file contains hidden or 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
…p history/slow disk waiting for git output, add detail presets for in-progress blame and uncommitted changes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Make blamer process asynchronous so VS doesn't lag on large files/deep history/slow disk waiting for git output, add detail presets for in-progress blame and uncommitted changes
Shows
Blame in progress..while the blamer is running, showsUncommitted changesfor (self explanatory) instead of the0000000hash with an excess of useless information. Doesn't show details on-hover for these two cases.Also makes quick summary more reliable i.e. showing up on launch, the first time a file is opened, when a view is moved into/out of a split pane or separate window, etc