While using diff-highlight with other tools, I have discovered that Python
ignores SIGPIPE by default. Unfortunately, this also means that tools
attempting to launch a pager under Python--and don't realize this is
happening--means that the subprocess inherits this setting. In this case, it
means diff-highlight will be launched with SIGPIPE being ignored. Let's work
with those broken scripts by explicitly setting up a SIGPIPE handler and exiting
the process.
Signed-off-by: John Szakmeister <j...@szakmeister.net>
---
contrib/diff-highlight/diff-highlight | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/contrib/diff-highlight/diff-highlight
b/contrib/diff-highlight/diff-highlight
index c4404d4..dfcc35a 100755
--- a/contrib/diff-highlight/diff-highlight
+++ b/contrib/diff-highlight/diff-highlight
@@ -14,6 +14,15 @@ my @removed;
my @added;
my $in_hunk;
+# Some scripts may not realize that SIGPIPE is being ignored when launching the
+# pager--for instance scripts written in Python. Setting $SIG{PIPE} =
'DEFAULT'
+# doesn't work in these instances, so we install our own signal handler
instead.
+sub pipe_handler {
+ exit(0);
+}
+
+$SIG{PIPE} = \&pipe_handler;
+
while (<>) {
if (!$in_hunk) {
print;
--
2.0.1
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
