Public bug reported:
Sometimes, when I exit mpg123 (by pressing ^C to send SIGINT to it,
which is the normal way to do so…) the prompt is in such state as
pressing Cur↑ shows ^[[A, which can be fixed by then pressing ^U
(invisible) and Enter, so that the cleanup that happens on every Enter
fixes it. (I could also blindly type another command or use it from
history. It also works, but this is annoying.)
I have absolutely no idea where that comes from, or how to debug it. I
suspect mpg123 lives for a bit longer after the ^C and messes up tty
state after the shell tried to restore it. Or, there is a race condition
in the shell making it not restore this properly after the signal
(which, after all, the shell does get).
Help welcome!
** Affects: mksh
Importance: Low
Status: Triaged
** Tags: help-wanted
--
You received this bug notification because you are a member of mksh
Mailing List, which is subscribed to mksh.
Matching subscriptions: mkshlist-to-mksh-bugmail
https://bugs.launchpad.net/bugs/1667506
Title:
Sometimes ^C leaves tty in weird state
Status in mksh:
Triaged
Bug description:
Sometimes, when I exit mpg123 (by pressing ^C to send SIGINT to it,
which is the normal way to do so…) the prompt is in such state as
pressing Cur↑ shows ^[[A, which can be fixed by then pressing ^U
(invisible) and Enter, so that the cleanup that happens on every Enter
fixes it. (I could also blindly type another command or use it from
history. It also works, but this is annoying.)
I have absolutely no idea where that comes from, or how to debug it. I
suspect mpg123 lives for a bit longer after the ^C and messes up tty
state after the shell tried to restore it. Or, there is a race
condition in the shell making it not restore this properly after the
signal (which, after all, the shell does get).
Help welcome!
To manage notifications about this bug go to:
https://bugs.launchpad.net/mksh/+bug/1667506/+subscriptions
