Re: Getting user input with STDOUT tee to file

I've noticed that occasionally, rather perversely, some programs use STDERR to perform user prompting ?!

system captures neither STDOUT nor STDIN and the command you issue captures only STDOUT - does the problem lie therein ?

A user level that continues to overstate my experience :-))

Comment on Re: Getting user input with STDOUT tee to file

Replies are listed 'Best First'.
Re^2: Getting user input with STDOUT tee to file by Marshall (Canon) on Oct 17, 2009 at 03:37 UTC
I've seen that too! ie, using STDERR inappropriately to do user communication. But in this case, if that was happening (a print of the question to STDERR), the OP would have seen the question on the screen. I suspect that in the OP's situation, it could be that unbuffering the output into the STDOUT pipe is a necessary, but not sufficient condition. The tee program also has to use unbuffered output! I updated my previous post with a link to another thread where I posted a simple program that demonstrates what $\|=1 does using only half a dozen print statements.	[reply]

Replies are listed 'Best First'.

Re^2: Getting user input with STDOUT tee to file
by Marshall (Canon) on Oct 17, 2009 at 03:37 UTC

I suspect that in the OP's situation, it could be that unbuffering the output into the STDOUT pipe is a necessary, but not sufficient condition. The tee program also has to use unbuffered output!

I updated my previous post with a link to another thread where I posted a simple program that demonstrates what $|=1 does using only half a dozen print statements.

[reply]