David Roundy <[EMAIL PROTECTED]> writes:
> It'd be better to keep output and errput interleaved as closely as
> possible. It's unfortunate that runInteractiveCommand doesn't support
> this, but you could look at franchise for an attempt to get some semblance
> of interleaving through use of threads. Without this, it's very hard to
> figure out which error messages go with which output.
That sounds[0] like almost the opposite of the unix convention of "give
me stderr ASAP (i.e. unbuffered), and stdout whenever (i.e. buffered)."
[0] I didn't look at the code, of course :P I'm lazy and tired and it's
my bedtime.
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
