This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
RE: TTYs and non-cygwin code...
- To: "gnu-win32 at cygnus dot com" <gnu-win32 at cygnus dot com>, "'kubitron at cs dot berkeley dot edu'" <kubitron at cs dot berkeley dot edu>
- Subject: RE: TTYs and non-cygwin code...
- From: Sergey Okhapkin <sos at prospect dot com dot ru>
- Date: Tue, 7 Apr 1998 13:39:55 +0400
John Kubiatowicz wrote:
> Forgive me if this is a misunderstanding, but is it the case that one
> cannot launch non-cygwin interactive applications from bash when tty
> support is turned on? I have seen this behavior for some applications,
The behavior depends of the application. When tty support is enabled,
stdin/stdout/stderr are redirected to a pipes, connected to "controlling
tty". If the application does ReadFile() or WriteFile() on this handles, it
works fine. For example, NT's cmd.exe started from bash works without
problems. But if the application uses console api calls with this handles,
it fails.
--
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".