One doubt: when using pipeOutputError, is it possible to take the output and error producers and consume them concurrently in separate threads, for example using the *Concurrently <http://hackage.haskell.org/package/async-2.0.2/docs/Control-Concurrent-Async.html#t:Concurrently> *applicative from *Control.Concurrent.Async*?
On Friday, March 20, 2015 at 5:42:57 PM UTC+1, Omari Norman wrote: > > Hi all, > > I have created a library, pipes-cliff, for interacting with subprocesses > using Pipes. > > http://hackage.haskell.org/package/pipes-cliff > > It aims to be simple and straightforward. It's not as powerful as > process-streaming--for instance you cannot combine standard output and > standard error into the same stream (at least, not without doing the work > yourself.) It doesn't do ByteString to Text conversions. But the API is > (hopefully) easier to understand and works for the simple use cases that I > need. > > See also this previous thread for discussions of the various issues > involved with streaming to and from subprocesses. > > > https://groups.google.com/forum/#!msg/haskell-pipes/JFfyquj5HAg/Lxz7p50JOh4J > > Feedback and bug reports welcome. Thanks. --Omari > -- You received this message because you are subscribed to the Google Groups "Haskell Pipes" group. To unsubscribe from this group and stop receiving emails from it, send an email to haskell-pipes+unsubscr...@googlegroups.com. To post to this group, send email to haskell-pipes@googlegroups.com.
