Follow-up Comment #1, bug #46273 (project screen):
(I'm not currently a developer, but am trying to gather more information about
the problem so if one comes along they have what they need.)
Can you install the "teseq" package, and then run the following commands:
$ script -tscreen.timings -c 'infocmp; screen script -tnmon.timings -c
"infocmp; nmon" nmon.scr' screen.scr
$ teseq -D -t nmon.timings nmon.scr nmon.tsq
$ teseq -D -t screen.timings screen.scr screen.tsq
And then attach the nmon.tsq and screen.tsq files to this report?
(When nmon runs, put it into whatever mode demonstrates the graphical
problems, let it run for a few seconds, and then quit.)
Developers: if you have the "teseq" package installed for your system
(available for most), you can translate the .tsq files back into the original
typescript/timing files with the "reseq" command; I mostly recommended the
translation with teseq because (a) it avoids missing control characters that
sometimes happen when people try to attach raw tyepscripts, (b) it's easier
than a typescript to read/evaluate for problems, (c) I wrote teseq when I was
a screen maintainer, to help me debug problems with screen, so I use it when I
have the chance :)
Thanks!
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?46273>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
