Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

Re: [windows] Non-blockable output to cmd console during text selection?

by BrowserUk (Patriarch)
on Jun 30, 2018 at 14:22 UTC ( [id://1217654]=note: print w/replies, xml ) Need Help??


in reply to [windows] Non-blockable output to cmd console during text selection?

Background information is that our provider changed the windows version and activated "QuickEdit mode" for consoles on default.

You can disable quick-edit mode from within the program using Win32::Console::Mode().

This may help.


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
  • Comment on Re: [windows] Non-blockable output to cmd console during text selection?
  • Download Code

Replies are listed 'Best First'.
Re^2: [windows] Non-blockable output to cmd console during text selection?
by LanX (Saint) on Jun 30, 2018 at 23:30 UTC
    Thanks, I will try this out.

    But is it also possible to activate an input buffer which keeps the output without freezing the Perl script?

    Much like a Linux terminal does?

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

      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

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1217654]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (4)
As of 2024-04-20 02:20 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found