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
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Mon, 28 Jun 1999 21:18:49 -0400
To: David Stuart <davidst AT nortelnetworks DOT com>
Cc: Chris Faylor <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: stty
Message-ID: <19990628211849.B15140@cygnus.com>
References: <FF7BD1DFC2ABD211A7580000F81AEB76BCDEB8 AT zmerd00d DOT ca DOT nortel DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <FF7BD1DFC2ABD211A7580000F81AEB76BCDEB8@zmerd00d.ca.nortel.com>; from David Stuart on Mon, Jun 28, 1999 at 08:04:56AM -0500

Since the 'tty emulation' mode uses pipes for communication, it does
cause some problems with programs who are expecting their stdin/stdout
to be an actual console.

If it is just vim that is giving you problems, then you can always use
a cygwin-specific version.

Basically, the only way you're going to be able to get the functionality
that you want is if you use pure-cygwin applications.  Even if a
non-cygwin program operates fine in CYGWIN=tty mode, it will not
understand Cygwin's conventions for setting things like 'intr', 'susp',
'kill', etc.

cgf

On Mon, Jun 28, 1999 at 08:04:56AM -0500, David Stuart wrote:
>this seems to result in somewhat unstable behavior for running DOS
>applications (vim and gvim, for example)..
>
>So I guess I will have to live with it not having all the stty settings,
>if I want to interwork with NT applications?
>
>Dave
>> -----Original Message-----
>> From:	Chris Faylor [SMTP:cygwin AT sourceware DOT cygnus DOT com]
>> Sent:	Saturday, June 26, 1999 2:04 PM
>> To:	Stuart, David [SKPK:1O21:EXCH]
>> Cc:	cygwin
>> Subject:	Re: stty
>> 
>> On Fri, Jun 25, 1999 at 01:49:45PM -0400, David Stuart wrote:
>> >Hi,
>> >
>> >I hope I'm not beating a dead horse by bringing this topic up, but has
>> >anyone figured out how to get the stty settings to work in bash?
>> >
>> >stty intr, susp, kill, etc.
>> >
>> >None of these commands seem to work, or work strangely (^C, for
>> instance).
>> >I realize it's probably a DOS/unix difference in the tty, but still,
>> >is there a workaround?
>> 
>> You can either set CYGWIN=tty prior to running bash or use a recent
>> snapshot.

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