Good point. Thanks.

If that causes problems for you, then you can always fix it to:

open STDERR, '>', 'NUL';
Or take it up a notch with File::Spec::Win32:
sub WinSetConsole { return $WIN32CONSOLE if $WIN32CONSOLE; require Win32::Console; import Win32::Console; { require File::Spec::Win32; my $devnull = File::Spec::Win32->devnull(); local *STDERR; open STDERR, '>', $devnull; $WIN32CONSOLE = Win32::Console-> new(Win32::Console->STD_INPUT_HANDLE); } return $WIN32CONSOLE; }

In reply to Re^3: non-XS version of Term::ReadKey? by Khen1950fx
in thread non-XS version of Term::ReadKey? by perl5ever

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.