GNOME Bugzilla – Bug 641974
Escape sequences are not being handled correctly
Last modified: 2018-03-27 17:47:31 UTC
Created attachment 180528 [details] Screenshots of printed escape characters It appears that gnome-terminal is not correctly emulating how an xterm handles escape sequences. My program uses ncurses to write a table of floating-point values to a console as it runs. If I run this program in an xterm, everything is fine. If I run it in gnome-terminal, escape characters and things like "[31;]" end up getting printed to the screen, overwriting the values (for an example, see the attached image). I'm sorry I can't provide more information, but I can't post our code. In gnome-terminal-2.32.0, $ echo $TERM xterm $ env|grep -i utf LANG=en_US.utf8 GDM_LANG=en_US.utf8
Please attach a script(1) log of the relevant part of the programme's output.
Two problems: 1. Can I edit a script log without making it useless? There are some parts I can't post publicly, so I'd need to remove some chunks. 2. When I run the program inside script, it behaves normally. The characters you see in the screenshot don't appear. Sorry. Let me know if there's anything else I can do to help.
I recorded a script log running in both xterm and gnome-terminal. I edited out several things, and as I mentioned above, the problem does not occur when script is recording the session, but at least you can look at it and see what it's writing. As the program runs, an ncurses display updates several floating-point values to a table on the screen. The script apparently shows the values being written, along with various other characters that seem to have something to do with where ncurses jumps to write new info. I hope this is helpful.
Created attachment 181609 [details] A partial typescript of the program running in an xterm
Created attachment 181610 [details] A partial typescript of the program running in a gnome-terminal
Mark, do you still experience this problem with newest vte?
Closing this bug now; there've been many many changes since this was opened and it's unclear if any issues still apply. If you find a similar problem on vte git master please report new bug(s, one per issue).