shell-conduit

shell-conduit copied to clipboard

Currently the only way to wire up conduits to the output of shell processes is `shell "blah" $| conduit myConduitPipeline` and it requires that `myConduitPipeline` both inputs and outputs bytestrings....

ProofOfKeags

First of all, thanks for a great library! Some entirely good Unix pipelines don't work in `shell-conduit` though. Consider: $ yes | head y y y y y y y...

firefrorefiddle

Add 'Semigroup' and 'Monoid' instances for 'Segment'

1

These instance would be really useful! ```haskell instance Semigroup r => Semigroup (Segment r) where () = liftA2 () instance Monoid r => Monoid (Segment r) where mempty = pure...

chshersh

Build failure when some programs are on the PATH

1

If any program in the PATH is called the same as any of the following identifiers, there is some risk that `Data.Conduit.Shell` fails to build as in: ``` shell-conduit $...

facundominguez

Tests fail on Darwin (macOS) when GNU coreutils are on the path

1

The tests for this program assume that running Darwin means that FreeBSD's coreutils are on the path, but that's not necessarily the case. With the Nix package manager, this breaks...

therealpxc

The function should print where it CD'ed to apart from CD'ing

psibi

Starting with TH 2.18 there is `putDoc` function appeared in API. So TH generated functions might have haddocks.

yaitskov

I would like to run process in background and wait on it or kill it later

yaitskov