On Fri, Sep 9, 2011 at 6:34 PM, Martin S. Weber <[email protected]>wrote:
> Really? I'm assuming the JSON output goes to stdout, and the error message > goes to stderr. In that case it wouldn't interfere with the JSON output at > all. Just pipe the output to your json reader without a 2>&1...there'll be > no problem. > Sorry, i wasn't clear - "interfere" meaning "aesthetically ugly." The JSON went where i told it to (stdout) but stderr was getting unexpected output. But i just found the reason, so i'm happy now :). -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
