Re: Xlib:sequece lost. Continued.

Alexander> Naturally, I did not remember, but when it happened a few more times I Alexander> tried to figure what may have triggered the problem ... Unfortunately, Alexander> no Alexander> pattern here... One time I was clicking the "File" meanu, the other time Alexander> I did nothing - the xemacs window was not even in focus. The only Alexander> subprocess Alexander> that was started (not before it froze, but in the beginning of xemacs Alexander> session) Alexander> was clearcase. Right. That indeed means it's a different problem (bummer): My patch only affects the subprocess code, and I had thought that's where all the async replies were coming from. Until now. The next step then is to set `x-debug-mode' to t and see what happens. Could you do that? Thanks for the report! -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla