Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <374ADEED.DD7CB53C@lbin.com>
Date: Tue, 25 May 1999 10:33:33 -0700
From: Ian Zimmerman <itz AT lbin DOT com>
Organization: Lightbinders, Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Cygnus tools mailing list <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: Cygwin built DLL invoked from MSC app doesn't seem to be all there.
References: <19990525171802 DOT 6724 DOT rocketmail AT send205 DOT yahoomail DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Earnie Boyd wrote:
> 
> --- Jon Wells <jon AT bigbang DOT com DOT au> wrote:
> > It's seems that only some bits of the cygwin API work inside a dll
> > invoked from a none cygwin applications.
> -8<-
> > Anyone got any thoughts? I getting really close to having to use
> > micromush tools and yucky ugly stuff like that..
> 
> To communicate properly between cygwin and non-cygwin processes you must have
> set notty in the CYGWIN variable before starting bash.

Why?  I thought (after reading the documents) that CYGWIN=tty just
enabled termios calls.  What harm does it do when cooperating with
non-cygwin programs?

-- 
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com