Do not expect users of Cygwin-Perl to see the expected behavior if you do employ the -t test to try to determine the context. An interactive shell will not be detected in that case.

I don't have a workaround for this, I merely have known it to be broken for a while now. I also do not know when (at what release of Perl) it broke (if it ever worked), or if it has since been fixed. It would be right nice, podners, if it WAS to be fixed, since people's Makefile.PLs that ask for user input at module build time are broken by this on Cygwin, too.

Update 19 Sept 2005

I concur that it seems to have been fixed in the latest releases on cygwin-perl. Yay!

    Soren A / somian / perlspinr / Intrepid

In reply to Re: Detecting interactive/non-interactive shell by Intrepid
in thread Detecting interactive/non-interactive shell by kosun

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.