You can use
long_running_command 1>&2 |& print_progress
The problem is that libc will line-buffer when stdout to screen, and full-buffer when stdout to a file. But no-buffer for stderr.
I don't think it's the problem with pipe buffer, it's all about libc's buffer policy.
damn but that doesn't work since it just spits out all data anyway :(
We just interviewed someone for my department the other day who is in the army reserves and one of the people from my team kept asking a bunch of intrusive questions about it
I know that is a pretty protected thing that cannot be used to discriminate employment so it made me uncomfortable they were asking so much about it lol
I'm pretty sure you can't even legally ask someone if they are married so I would imagine asking a bunch of questions about their reserve status isn't kosher
So after all that work trying to process the output from that troublesome command I think I'm probably going to end up using an entirely different method altogether :(
You can use
long_running_command 1>&2 |& print_progress
The problem is that libc will line-buffer when stdout to screen, and full-buffer when stdout to a file. But no-buffer for stderr.
I don't think it's the problem with pipe buffer, it's all about libc's buffer policy.
