From 924e9702036d8a1506cc6bb07facb18e23494519 Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <schwinge@nic-nac-project.de>
Date: Thu, 8 Oct 2009 09:26:42 +0200
Subject: open_issues/bash_vs_screen_vs_sigint: MIG reply error isolated to
 PROMPT_COMMAND being set.

---
 open_issues/bash_vs_screen_vs_sigint.mdwn | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/open_issues/bash_vs_screen_vs_sigint.mdwn b/open_issues/bash_vs_screen_vs_sigint.mdwn
index f5ce5166..47d79c65 100644
--- a/open_issues/bash_vs_screen_vs_sigint.mdwn
+++ b/open_issues/bash_vs_screen_vs_sigint.mdwn
@@ -65,5 +65,24 @@ this:
 
 To sum up:
 
-  * *bash*: 4.0 packages have the MIG reply error.
   * <strike>*screen*: new package causes that invokee doesn't react to `C-c` anymore.</strike>
+
+  * *bash*: 4.0 packages have the MIG reply error.
+
+    After having noticed that this error doesn't occur if starting *bash* with
+    `--norc`, I isolated it to the following command in `.bashrc`:
+    
+        case $TERM in
+          xterm* | rxvt*)
+            PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}:${PWD}\007"';;
+        esac
+
+    ... and indeed:
+
+        tschwinge@flubber:~ $ echo "$TERM" -- "$PROMPT_COMMAND"
+        xterm -- echo -ne "\033]0;${USER}@${HOSTNAME}:${PWD}\007"
+        tschwinge@flubber:~ $ ^C
+        -bash: echo: write error: (ipc/mig) wrong reply message ID
+        tschwinge@flubber:~ $ PROMPT_COMMAND=
+        tschwinge@flubber:~ $ ^C
+        tschwinge@flubber:~ $ 
-- 
cgit v1.2.3