Didier Verna <verna(a)inf.enst.fr> writes:
> The right solution is for x_IO_error_handler to throw to top
level
> without ever returning to Xlib.
This sounds like it will fix your problem, but not the case where
one of *multiple* X connections (either local or remote) is killed,
right ?
Why? I thought it would fix both. I haven't tested it yet, though.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
"Listen, kid, we're all in it together!" -- Harry Tuttle in _Brazil_