Sönke Hahn
Working on this in earnest in #210. I'll keep this open for reference until that lands.
I think there's two related but separate issues here. I'll try to explain: When a child process writes something to `stdout`, in `cradle` there's currently two things you can do...
I see. Yeah, it sounds like `pacman` uses something like [`isatty`](https://man7.org/linux/man-pages/man3/isatty.3.html) to decide what it writes to `stdout` or `stderr`. Thanks for the reply! (I think `cradle` could in theory...
If we'd have a `BoxedInput`, then users could also do something like: ``` rust let mut args: Vec = vec!["foo".boxed(), "bar".boxed(), LogCommand.boxed()]; if condition { args.push(Stdin("input").boxed()); } args.run(); ``` With...
Yeah, I was also thinking that a wrapper type might be necessary. Out of curiosity, what exactly is the advantage of using `IntoIterator` over `Iterator` here?
Yeah, that seems like a good idea. At least if it's not too complicated to implement. But I don't think it should be. I wouldn't want to export it by...
Yeah, that seems good too. I had hoped that the generated documentation would show a `This is supported on Unix only.` label if an item has a `#[cfg(unix)]`. But that...
Or maybe `cradle::unix` is good enough? And would make it clearer at the top-level, what's going on.
I like this idea. I'm a bit worried about having to re-implement `bash`'s expansion behavior.
Yeah, that's a really good idea. I think it'd be worth creating a PR that implements this to see how this interacts with e.g. the `String` impl. Or whether this...