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.

In reply to Re^2: Getting user input with STDOUT tee to file by Marshall
in thread Getting user input with STDOUT tee to file by xjlittle

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.