status code and stderr for %% #207
Comments
Yeah, I haven't figured out how to make I wonder if the early-termination problem is something to do with not fully consuming the output Do you have a nice self-contained repro of the problem I can add to my test suite? That'd make it easier to attack |
regarding the api, how about giving the return value a lazy member |
yeah seems reasonable. Some kind of structured data would be nice. The whole lazy-vs-strict thing is kinda still in flux; right now most things are strict, so we could make this strict as well and figure out how to make lazy things lazy later if we decide we care |
If we end up with something more flexible to deal with the |
sounds good. structured data for what? |
Structured data so we can access things like the output stream, error stream, exit code, and other things without having to have 100 different |
agreed |
Fixed by 5d7fb68, will go out in 0.5.1 |
awesome :)! |
Would be great if %% would return not only the stdout but also stderr and status code. Also, it seems %% is broken in that it terminates commands too early. I tried to use it with tar and ended up with empty or broken archives while % works fine, but writes all output to stdout.
The text was updated successfully, but these errors were encountered: