From fc2488eb1ebe33ecd88880138fc640e4aafcb3cb Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Wed, 7 Oct 2009 22:15:31 +0200 Subject: open_issues/bash_vs_screen_vs_sigint: A few bash issues are the same on GNU/Linux. --- open_issues/bash_vs_screen_vs_sigint.mdwn | 23 +++++++++++------------ 1 file changed, 11 insertions(+), 12 deletions(-) diff --git a/open_issues/bash_vs_screen_vs_sigint.mdwn b/open_issues/bash_vs_screen_vs_sigint.mdwn index 8dbb6816..371b622e 100644 --- a/open_issues/bash_vs_screen_vs_sigint.mdwn +++ b/open_issues/bash_vs_screen_vs_sigint.mdwn @@ -29,30 +29,30 @@ this: * GNU/Hurd; Debian package 4.0-4 / `$BASH_VERSION` is `4.0.28(1)-release`; *libc0.3* Debian package 2.9-25 * plain - * shell prompt: **`^C`, then new line, then `-bash: echo: write error: (ipc/mig) wrong reply message ID`**, then new line / prompt printed; `$?` is **128**. - * `sleep 10` running: **`^C` printed**, SIGINT is sent; `$?` is 130. + * shell prompt: `^C`, then new line, then **`-bash: echo: write error: (ipc/mig) wrong reply message ID`**, then new line / prompt printed; `$?` is 128. + * `sleep 10` running: `^C` printed, SIGINT is sent; `$?` is 130. * in a *screen* session (Debian package 4.0.3-11) - * shell prompt: **`^C`, then new line / prompt printed**; `$?` is **128**. - * `sleep 10` running: **`^C` printed**; SIGINT is sent; `$?` is 130. + * 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 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.) + error in the not-*screen* case, and, when in command-line editing mode, the + displaying of `^C` (same on GNU/Linux), and the 128 value for `$?` (same on + GNU/Linux). * GNU/Hurd; Debian package 4.0-7 / `$BASH_VERSION` is `4.0.33(1)-release`; *libc0.3* Debian packages 2.9-19, 2.9-25, 2.9-27 * plain - * shell prompt: **`^C`, then new line, then `-bash: echo: write error: (ipc/mig) wrong reply message ID`**, then new line / prompt printed; `$?` is **128**. + * shell prompt: `^C`, then new line, then **`-bash: echo: write error: (ipc/mig) wrong reply message ID`**, then new line / prompt printed; `$?` is 128. * `sleep 10` running: `^C` printed; SIGINT is sent; `$?` is 130. * in a *screen* session (Debian package 4.0.3-11) - * shell prompt: **`^C`**, then new line / prompt printed; `$?` is **128**. + * shell prompt: `^C`, then new line / prompt printed; `$?` is 128. * `sleep 10` running: `^C` printed; SIGINT is sent; `$?` is 130. This is equivalent to the *bash* 4.0-4 / 4.0.28(1) behavior. * GNU/Hurd; Debian package 4.0-7 / `$BASH_VERSION` is `4.0.33(1)-release`; *libc0.3* Debian package 2.9-27 * plain - * shell prompt: **`^C`, then new line, then `-bash: echo: write error: (ipc/mig) wrong reply message ID`**, then new line / prompt printed; `$?` is **128**. + * shell prompt: `^C`, then new line, then **`-bash: echo: write error: (ipc/mig) wrong reply message ID`**, then new line / prompt printed; `$?` is 128. * `sleep 10` running: `^C` printed; SIGINT is sent; `$?` is 130. * in a *screen* session (Debian package 4.0.3-14) * shell prompt: **no reaction (nothing printed)**; `$?` thus is **unchanged**. @@ -63,6 +63,5 @@ this: To sum up: - * *bash*: 4.0 packages print `^C` at the shell prompt, have the MIG reply - error, and the difference in the value 128 for `$?`. + * *bash*: 4.0 packages have the MIG reply error. * *screen*: new package causes that invokee doesn't react to `C-c` anymore. -- cgit v1.2.3