Comment 13 for bug 1566437
Revision history for this message
| Egmont Koblinger (egmont-gmail) wrote | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
> I found a hacky workaround - add this to your $PS1:
The workaround of resetting relevant settings from the prompt has already been mentioned – although without showing a concrete example.
> Given how randomly it happens, I believe there is a real bug in Terminator
I'm about 99.999% sure that this is _not_ a bug in Terminator (VTE). It is believed to properly execute the relevant escape sequences it receives. (Can you reproduce the issue with xterm, urxvt, konsole...? I bet you can.)
> but if you want to force the broken state, just open 'mc' and run 'pkill mc' from another terminal, your scrolling will be broken.
Yup, in this case mc asks the terminal to switch to a special mode, and due to getting killed, it does not ask the terminal to leave that mode. Nothing new here, exactly what has already been concluded in this thread.
> run e.g 'mc > trace.txt'. Then type 'exit', hit return, and mc will quit. You will get all the escape sequences from mc in trace.txt to inspect.
Can you really reproduce the issue this way? Because you don't kill mc now, but exit it cleanly.
> to report it as a terminator bug
Unless you have firm evidence that this is a terminator (or VTE) bug, please don't spam its bugtracker with something that's most likely an issue elsewhere.