delorie.com/archives/browse.cgi | search |
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: | <75F8791C7793D211B64D080036DE1504151C83@milton.sonosight.com> |
From: | "Stewart, Wayne" <wayne DOT stewart AT sonosite DOT com> |
To: | "'Chris Faylor'" <cgf AT cygnus DOT com> |
Cc: | "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com> |
Subject: | RE: Problems with stdio & stderr |
Date: | Thu, 29 Apr 1999 11:12:10 -0700 |
MIME-Version: | 1.0 |
X-Mailer: | Internet Mail Service (5.5.2448.0) |
> > 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. > > -chris > 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? It also leads me to beleive that it would be *very* difficult to port these to Mingw32, no? (How do you pronounce "mingw32" anyway?) What about the emacs shell issue? Is this more easily addressed? Thanks, Wayne -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |