summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Schwinge <schwinge@nic-nac-project.de>2009-10-08 09:26:42 +0200
committerThomas Schwinge <schwinge@nic-nac-project.de>2009-10-08 10:00:17 +0200
commit924e9702036d8a1506cc6bb07facb18e23494519 (patch)
treea61b4e8eff9543e9acaa33938ecf2630b865db34
parent771bd0745a4d7eb990ce8d42f8ae7b4f163c4dfb (diff)
open_issues/bash_vs_screen_vs_sigint: MIG reply error isolated to PROMPT_COMMAND being set.
-rw-r--r--open_issues/bash_vs_screen_vs_sigint.mdwn21
1 files changed, 20 insertions, 1 deletions
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:~ $