summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Schwinge <schwinge@nic-nac-project.de>2009-10-03 16:08:37 +0200
committerThomas Schwinge <schwinge@nic-nac-project.de>2009-10-03 16:08:37 +0200
commit78188ccfd77b9d5c6a0e95232536cdabc616bd85 (patch)
tree51cfe3b100e16834bdd39be06bbb858b4394d5bf
parent9a04763a922a8f5084035d44eadd35709958fedc (diff)
open_issues/bash_vs_screen_vs_sigint: Improve.
-rw-r--r--open_issues/bash_vs_screen_vs_sigint.mdwn8
1 files changed, 4 insertions, 4 deletions
diff --git a/open_issues/bash_vs_screen_vs_sigint.mdwn b/open_issues/bash_vs_screen_vs_sigint.mdwn
index 8260b004..c8a31a15 100644
--- a/open_issues/bash_vs_screen_vs_sigint.mdwn
+++ b/open_issues/bash_vs_screen_vs_sigint.mdwn
@@ -35,7 +35,7 @@ this:
* shell prompt: **`^C`, then new line / prompt printed**; `$?` is **128**.
* `sleep 10` running: **`^C` printed**; SIGINT is sent; `$?` is 130.
- This differs from the behavior of the earlier *bash* version in the MIG
+ This differs from the behavior of the earlier *bash* version in the MIG reply
error in the not-*screen* case, and in the **128** value for `$?`. The
former is an error, and the latter may be as expected. (Check GNU/Linux
with that *bash* version.)
@@ -63,6 +63,6 @@ this:
To sum up:
- * *bash*: 4.0 packages have the MIG error, and the 128 return value difference.
-
- * *screen*: new package doesn't react to `C-c` anymore.
+ * *bash*: 4.0 packages print `^C` at the shell prompt, have the MIG reply
+ error, and the difference in the value 128 for `$?`.
+ * *screen*: new package causes that invokee doesn't react to `C-c` anymore.