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
Date: Thu, 29 Apr 1999 14:46:39 -0400
From: "'Chris Faylor'" <cgf AT cygnus DOT com>
To: "Stewart, Wayne" <wayne DOT stewart AT sonosite DOT com>
Cc: "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: Problems with stdio & stderr
Message-ID: <19990429144639.C12911@cygnus.com>
References: <75F8791C7793D211B64D080036DE1504151C83 AT milton DOT sonosight DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <75F8791C7793D211B64D080036DE1504151C83@milton.sonosight.com>; from Stewart, Wayne on Thu, Apr 29, 1999 at 11:12:10AM -0700

On Thu, Apr 29, 1999 at 11:12:10AM -0700, Stewart, Wayne wrote:
>> expect relies on cygwin ptys to do its magic.  It is unlikely that
>> you'll be able to make things work if you are trying to use non-cygwin
>> functions for reading and writing.
>
>This seems to imply that expect/dejagnu are only useful for
>automating/testing "pure" Cygwin applications.  Is that the intent, or
>is the goal to make them more general purpose tools for the Win32
>platform eventually?

The intent of getting expect/dejagnu working was to allow us to test
the tools that we use here which are all based on cygwin.  Expect is
nearly there but there are still some problems.

We do not have any need to get expect working with generic Win32
tools so there are no plans to do so.

As usual, however, we gladly accept net contributions.

>It also leads me to beleive that it would be *very*
>difficult to port these to Mingw32, no?

Right.

>What about the emacs shell issue?  Is this more easily addressed?

I have no idea.  Sorry.

-chris

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