I’ve been seeing this for the last few years too, together with occasional
blocks on redisplay that take far too long to time out. As I understand it,
screen(1) plays games with various socket options, which causes the latter,
and may intercept SIGWINCH and the rest of the infrastructure for signalling
to an app that its terminal has been changed.
But, as you mention, 21.4 doesn’t have a problem, so we did something in the
course of 21.5 to provoke this. A binary search through the 21.5 releases
would narrow it down considerably, and with a bit of work with CVS it should
be possible to isolate the actual commit.
Ar an seachtú lá is fiche de mí na Samhain, scríobh Ron Isaacson:
Hi all --
This is a bit of a weird one... when using XEmacs 21.5 inside
screen(1), and using multiple frames, XEmacs sometimes goes bonkers
when I resize the terminal window.
I've got a set of steps to reproduce the problem, using:
- RedHat Linux (tried EL3 and FC5)
- XEmacs 21.5.27
- screen 4.00.02
- Any type of terminal (PuTTY, xterm, etc.)
Here are the steps:
1. Open an 80x24 terminal window, and start screen.
2. Inside screen, start xemacs, and use C-x 5 2 to create a new
frame. Type "Hello".
3. Resize the terminal to something larger than 80x24. You should
notice that XEmacs APPEARS to handle the resize correctly -- your
"Hello" is in the top-left corner, and the modeline moves to the
bottom and spans the full width of the terminal.
4. Now try typing. Does everything work normally?
When I do this, XEmacs seems to behave as if it's inside a terminal
that's only 2 characters wide x 3 characters tall, positioned in the
top-left corner of the real terminal. If I press M-<, what I actually
H$ <-- truncated "Hello"
-- <-- the modeline
M\ <-- truncated "Mark set" from M-<
Recovering from this is very tricky. It's not enough to put the
terminal back to its previous size; I need to actually delete the
frame (C-x 5 0), and sometimes still adjust the size of the terminal
for it to really recover.
Using 21.4, everything seems to work correctly. And with no frames,
there's no problem. Anybody know what might be going on here? Any
suggestions for how I might track this down?
ron.isaacson(a)morganstanley.com / (212) 276-1144
¿Dónde estará ahora mi sobrino Yoghurtu Nghé, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
XEmacs-Beta mailing list