Re: Process output problem?

Some time ago, Ben Wing wrote... |+ | I thought there was already an event loop for stream consoles? Under Unix, you can | type xemacs -batch -l dunnet. Cool... Even more cool it does not work under Windows (next-event blocks forever), I have to investingate how to fix it (select_console_cb currently does nothing). No, I meant bare temacs, which does not have an event stream at all. There could be an "event stream lite", which is capable only of selecting single process and generating only process events. In this case, call-process can be emulated by (let ((p (start-process ...))) (while (eq (process-status p) 'run) (accept-process-output p))) Kirill | Kirill M. Katsnelson wrote: | | > Some time ago, Andy Piper wrote... | > |+ | > | I notice that process output under cygwin is not triggering the correct | > | output coding. For instance doing vc-diff with cvs generates a buffer full | > | of ^M's, does anyone else see this under the native port? | > |- | > | > This is expected. Look into callproc.c, there are some parts of code dealing | > with CR/LF directly, not using lstreams. I am going to merge callproc and process | > code together but probably not for 21.0 release, because this is hairy, as this | > will require some "event loop" for an initial stream console, because call-process | > must work in bare temacs. | > | > Meanwhile, you can just extend preporicessor conditions to make that code compiled | > in under cygwin too. |-