Update: Actually, tee nul will work okay of you disable buffering on the output of your script:

perl -le"$|++;print 'x'x80 while do{ 1 for 1..1e7;1}" | tee nul

That'll allow the script to keep running whilst the console is in a select state, until the pipe fills, and then the script will again stall; but that would be the same on a linux console also I think.


It already has an associated buffer called the console screen buffer, and you can create as many of these as you like, though only one can be active at any given time.

But these are not 'simple' fifo-like stream buffers, but rather fully random access (by program and user) 2D arrays of characters and attributes. I'm not saying better or worse, just different.

The simple way to provide the isolation you want is to put some other program in charge of the screen, an use a fifo between your script and that other program.

In *nix terms, use a pipe: yourScript.pl | tee nul would probably do it, except now your script has to output 4k before anything shows up on screen at all.

So, running this:

perl -le"$|++;print 'x'x80 while do{ 1 for 1..1e7;1}" | perl -e"$|++; +print while <>"
allows the first script to continue to run flat out, even whilst the second script which has control of the console buffer is blocked in a select state.

(But disabling selection for the duration of the script is easier.)


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". The enemy of (IT) success is complexity.
In the absence of evidence, opinion is indistinguishable from prejudice. Suck that fhit

In reply to Re^3: [windows] Non-blockable output to cmd console during text selection? (Updated). by BrowserUk
in thread [windows] Non-blockable output to cmd console during text selection? by LanX

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.