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
The runtime of difft depends on the inputs, hardware, state of the system, etc. Often, --byte-limit and --graph-limit are used to limit the maximum user time. But they are approximations. As difft improves, the ideal limits change, but limits set in dotfiles linger. A solution that fits user needs, and is robust under changes of inputs, difft, hardware etc: --time-limit, which reverts to a text diff (or a --fallback-diff passed in) after a set amount of time is used.
Thanks for working on difft, which I use every day and which is amazing. This is just a feature request, no worries if its out of scope.
The text was updated successfully, but these errors were encountered:
melonmouse
changed the title
Add a --time-limit?
[feature] Add a --time-limit?
Feb 11, 2025
To my surprise, it seems git diff or difft automatically reverts to a text-only diff if difft fails (so on time-out, no explicit call to the fallback diff was needed in the above script).
The runtime of difft depends on the inputs, hardware, state of the system, etc. Often, --byte-limit and --graph-limit are used to limit the maximum user time. But they are approximations. As difft improves, the ideal limits change, but limits set in dotfiles linger. A solution that fits user needs, and is robust under changes of inputs, difft, hardware etc: --time-limit, which reverts to a text diff (or a --fallback-diff passed in) after a set amount of time is used.
Thanks for working on difft, which I use every day and which is amazing. This is just a feature request, no worries if its out of scope.
The text was updated successfully, but these errors were encountered: