-
Notifications
You must be signed in to change notification settings - Fork 405
New issue
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
🚀 ignore big file diff #288
Comments
Hi @swuecho, thank you! Can you tell me, which of these is closest to your problem?
Yes, there is. You can use the # Disable delta
git config --global --unset core.pager
# Enable delta
git config --global core.pager delta You can use that to set any git config option (git options and delta options): there are a few examples in the delta README. |
FWIW, Just call git as |
Hi @Kr1ss-XD, yes that's true that it modifies our gitconfig files on disk. However,
But... So I think for that reason I am currently embracing the idea of using my gitconfig as something that can be transiently mutated (I keep it in git, of course, so I can see the changes), and using aliases based on |
Agreed, those are good points. |
set alias to those as suggested by @Kr1ss-XD works great. it is a long line of json, which is the result of snapshot test. |
Thanks @swuecho I'm going to make fixing this/#154 my next task. That's an interesting idea about a timeout. Delta only has a single thread at the moment, but it could be fun to learn how to do the timeout in Rust. However, hopefully we can avoid any such hangs by truncating long-lines or emitting them raw. |
Fixed in master branch (not released yet) |
really like delta to show the diff but not usable when file too big.
when file is too big, delta will be no response. wonder if there is a way to stop diff specific file.
also, is there a way to tell git to stop using delta by some command line option while keep the git config unchanged? (I want to use delta by default, but when it does not work, I want to use the default git diff).
Thanks.
The text was updated successfully, but these errors were encountered: