Re: Internal error: lstream not open

kitty> It seems to happen when Gnus closes the connection with the NNTP server kitty> after lying idle for a while. I don't get a crash however. YMMV. This is kitty> with CVS updated just a while ago today. It's quite the reverse, actually: the connection times out, but XEmacs doesn't close the process associated with it: apparently Ben snipped some code for the great process-stderr patch. The attached patch should fix it. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla Index: src/event-stream.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/event-stream.c,v retrieving revision 1.69 diff -u -r1.69 event-stream.c --- src/event-stream.c 2002/06/20 21:18:29 1.69 +++ src/event-stream.c 2002/06/30 16:28:55 ＠＠ -3104,6 +3104,19 ＠＠ to enable that check, and we do so now. */ kick_status_notify (); } + else + { + /* Deactivate network connection */ + Lisp_Object status = Fprocess_status (p); + if (EQ (status, Qopen) + /* In case somebody changes the theory of whether to + return open as opposed to run for network connection + "processes"... */ + || EQ (status, Qrun)) + update_process_status (p, Qexit, 256, 0); + deactivate_process (p); + status_notify (); + } /* We must call status_notify here to allow the event_stream->unselect_process_cb to be run if appropriate. ＠＠ -3117,8 +3130,8 ＠＠ status_notify() will be called on return to top-level. */ status_notify (); - return; } + return; } case timeout_event: