From: cgf AT bbc DOT com (Christopher Faylor)
Subject: Re: One way to get around the cygwin terminal problem
16 Dec 1997 14:21:23 -0800
Message-ID: <ELAsDA.4tp.cygnus.gnu-win32@bbc.com>
References: <199712161108 DOT LAA89738 AT out2 DOT ibm DOT net>
Reply-To: cgf AT bbc DOT com
To: gnu-win32 AT cygnus DOT com

In article <199712161108 DOT LAA89738 AT out2 DOT ibm DOT net>,  <vischne AT ibm DOT net> wrote:
>vischne AT ibm DOT net wrote:
>>
>> In other words, with some work, it is possible to get a professional
>> looking and acting terminal application using the cygwin Unix
>> environment but bypassing the cygwin terminal window.
>
>>>It's a bad idea to replace stdout with direct console writings. You
>application, for example, will not work in a telnet session or in xterm
>window. <<
>
>Oh, now I know why you wrote this.  Your implementation of cygwin.dll and
>BASH-4.01$ doesn't support generation of a new console buffer to overlay
>the cygwin console buffer.  In fact, your web site claims that such
>applications won't work.  Tsk, tsk, tsk.  How can you claim that is an
>improvement?  I stopped using your earlier developmental binaries because
>they broke so many of the things that I had come to take for granted with
>cygwin b18.

That's interesting.  I'm sure that you understand that Sergey's
"developmental binaries" actually represent snapshots of Cygnus's own
development tree, right?  So, you were undoubtedly really diligent in
reporting all of this "broken" behavior so that it would be corrected
for B19.

Phew.  That's a relief.
-- 
http://www.bbc.com/	cgf AT bbc DOT com			"Strange how unreal
VMS=>UNIX Solutions	Boston Business Computing	 the real can be."
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".