From: cgf AT cygnus DOT com (Christopher G. Faylor)
Subject: Re: Tty support defaults
15 Apr 1998 05:22:51 -0700
Message-ID: <Pine.SUN.3.91.980415081846.22419A-100000.cygnus.cygwin32.developers@tweedledumb.cygnus.com>
References: <199804150808 DOT BAA21378 AT rtl DOT cygnus DOT com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
To: Geoffrey Noer <noer AT cygnus DOT com>
Cc: jeffdb AT goodnet DOT com, cygwin32-developers AT cygnus DOT com


On Wed, 15 Apr 1998, Geoffrey Noer wrote:

> > The notty default causes needless lockups, and, I don't see
> > any reason why we would want to have it turned off.
> > comments?
> 
> It sounds like we may be moving in the direction of putting some more
> effort into the tty layer soon.  If we decide to this and it proves
> feasible, we would change things so that the tty layer was always on
> while still permitting non-Cygwin32 console applications to run.
> Currently, if tty mode is on, some console apps like the non-Cygwin32
> version of vim can't run from bash which is very annoying.
> 
> I completely agree that having a tty mode is not desirable in
> principle.  For now though it's better than having it always on, IMHO.

I agree.  I don't understand the reason for the lockups in the console
mode version.  I haven't experienced them.  But, they should be fixed.

Maybe eventually, we'll want to have some method for marking specific
binaries as "notty" by default.