This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: STDIN and STDOUT not connected to a terminal?

On Mon, Nov 10, 2003 at 10:44:51AM -0800, Brown, Victoria wrote:
>I read the FAQ; I found nothing.
>I looked in the archives (obvious from my posting).
>"Smart questions" (ESR notwithstanding) are in the eye of the beholder.

>The folks at ActiveState cannot reproduce this problem; they _can_ run
>ppm with the latest version of cygwin bash.

>This is Perl 5.8.0
>Windows 2000 Pro
>theoretically latest cygwin (I installed it recently)
>CYGWIN='ntsec tty'

ActiveState perl is not a cygwin application.  It doesn't understand
cygwin ttys.  If you remove the 'tty' from the settings then -t will
probably work in a standard cygwin console.  It will not work right with
applications like 'rxvt' or 'ssh' which use cygwin ptys.  There is
no workaround for this other than using cygwin's perl.

>If there is something more you need to know, then please _tell me what
>it is_.  Don't be cryptic.

In the interests of helping you send a smarter question next time, here
is how you could have sent your message so that it would not require
several readings to figure out what was wrong:

*I am using ActiveState perl.  I've noticed that the following one line
*application does not display 'is a tty':
*perl -le 'print "is a tty\n" if -t STDIN'
*My cygcheck output is attached as per ."
Please use the resources at rather than sending personal email.
Special for spam email harvesters: send email to
and be permanently blocked from mailing lists at

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]