From: jeffdbREMOVETHIS AT goodnet DOT com (Mikey) Subject: Re: Tty support defaults 16 Apr 1998 07:53:19 -0700 Message-ID: <353a1939.43750771.cygnus.cygwin32.developers@smtp.goodnet.com> References: Reply-To: jeffdbREMOVETHIS AT goodnet DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Christopher G. Faylor" Cc: Geoffrey Noer , jeffdb AT goodnet DOT com, cygwin32-developers AT cygnus DOT com Hi Chris ;^) to reproduce the bug. fire up 95 set CYGWIN32=notty (or just leave unset) bash ^C for file in *;do rm ../$file;done #to get file not found errors LOCKUP!!! On Wed, 15 Apr 1998 08:21:40 -0400 (EDT), you wrote: > >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. ===================================================== Linux a platform built by, and for users, standing on the firm legs of reliability, and speed. Microsoft Windows, a platform without a leg to stand on. (jeffdbREMOVETHIS AT goodnet DOT com) delete REMOVETHIS from the above to reply Mikey