-
Notifications
You must be signed in to change notification settings - Fork 365
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
External diff tool exiting with code 1 should not cause a warning #5250
Comments
It's not an error but a warning for that reason. Maybe we can add a per-tool list of expected exit codes to suppress the warning. fwiw, you might want to set up |
Comment from PR (#5257 (review)):
I'm in favor of a wrapper. Minimal example: #!/usr/bin/env bash
diff "$@"
status=$?
case $status in
0 | 1) ;;
*)
# custom handling, etc
exit $status
;;
esac |
That works for e.g. Should I file a separate issue for that? |
I don't know if it's relevant, but there's a specific note for configuring |
Description
diff uses exit code 0 to signal that there were no changes, 1 to signal that there were changes, and an exit code >1 to signal an error. Tools like
delta
do the same, but jj treats exit code 1 as a problem.Steps to Reproduce the Problem
jj diff --config ui.diff.tool=diff
orjj diff --config ui.diff.tool=delta
Expected Behavior
No warnings show up.
Actual Behavior
The output ends with:
Specifications
The text was updated successfully, but these errors were encountered: