You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently started using diff-so-fancy. I really like the way new files are being shown. I used to miss them when scrolling quickly even with diff-highlight, that doesn't happen anymore.
What happens to me now is that I miss the beginning of a new commit when running a command like git log -p.
Suggestion: similarly to how files are shown like:
The rationale behind it is: file diffs and part of a commit. Hence the graphical representation of a commit should be "larger" than the one for each file. Similarly to how "Title1" is often displayed in a larger font than "Title2", in docs for example.
Cheers.
The text was updated successfully, but these errors were encountered:
Hello, I have just updated #398 with a new PR #497, which rebases the original one to the current next so that it can be merged without conflicts. I have tested it on my machine and it seems to still work well.
I think it would be a shame to let all the work done by @ericbn go to waste, so I'm writing hoping that the PR can be merged as it seems to be a really useful addition when examining lists of commits.
I recently started using
diff-so-fancy
. I really like the way new files are being shown. I used to miss them when scrolling quickly even withdiff-highlight
, that doesn't happen anymore.What happens to me now is that I miss the beginning of a new commit when running a command like
git log -p
.Suggestion: similarly to how files are shown like:
could commits look like:
The rationale behind it is: file diffs and part of a commit. Hence the graphical representation of a commit should be "larger" than the one for each file. Similarly to how "Title1" is often displayed in a larger font than "Title2", in docs for example.
Cheers.
The text was updated successfully, but these errors were encountered: