You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While writing a function to add Hitch info to my bash prompt, I was piping the output of hitch to cut, and wasn't getting any output. At first I thought I was doing something wrong in bash, but ultimately I discovered that Hitch.print_info is explicitly checking if STDOUT is a terminal and not outputting anything in that case. This prevents UNIX pipes from passing along the output of the command. Is there a reason this check is being made? Can it just be removed?
The text was updated successfully, but these errors were encountered:
At one point in time we had a hitch --info or --short that was used for this specific reason. It must have been lost in the major refactor I did a while back. I'll look into adding that back in for this.
While writing a function to add Hitch info to my bash prompt, I was piping the output of
hitch
tocut
, and wasn't getting any output. At first I thought I was doing something wrong in bash, but ultimately I discovered thatHitch.print_info
is explicitly checking ifSTDOUT
is a terminal and not outputting anything in that case. This prevents UNIX pipes from passing along the output of the command. Is there a reason this check is being made? Can it just be removed?The text was updated successfully, but these errors were encountered: