On Wed, Apr 16, 2008 at 8:54 PM, Krasimir Angelov <[EMAIL PROTECTED]>
wrote:

>
> This is really a bug. There is a code in Visual Haskell that executes
> an external process and then the stderr and stdout are read
> simulteniously and the output that is produced in the window should be
> a mixture of stderr and stdout. That is why any solution that uses
> hGetContents is clearly wrong. I thought that the necessary code can
> be just borrowed from Visual Haskell but if there is already something
> in Yi then it is ok.


Interleaving and incrementally updating the compile output buffer turned out
to be pretty trivial with the Subprocess support -- the only thing missing
that I can see is some sort of notification about whether the command
succeeded or not (which is why cabalConfigureE still waits for runhaskell to
finish).  I think a callback argument to createSubprocess would do the trick
here quite neatly, but I'll spend some more time with the source before
jumping into that sort of change.

cheers,
Fraser.

--~--~---------~--~----~------------~-------~--~----~
Yi development mailing list
[email protected]
http://groups.google.com/group/yi-devel
-~----------~----~----~----~------~----~------~--~---

Reply via email to