Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Andrew DeFaria Subject: Re: How can I avoid using a DOS box?? Date: Wed, 27 Nov 2002 11:23:01 -0800 Lines: 20 Message-ID: <3DE51B95.8040303@Salira.com> References: <1038398679 DOT 16091 DOT 23 DOT camel AT lifelesswks> <20021127153546 DOT GE6924 AT redhat DOT com> NNTP-Posting-Host: 206.184.204.2 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1038424940 3347 206.184.204.2 (27 Nov 2002 19:22:20 GMT) X-Complaints-To: usenet AT main DOT gmane DOT org NNTP-Posting-Date: Wed, 27 Nov 2002 19:22:20 +0000 (UTC) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en, ru, zh Christopher Faylor wrote: > I don't know how often I've expressed my opinion but I am mildly against > it. The problem is that cygwin's pty implementation is not perfect. It > can't run some native windows programs and it can deadlock occasionally. > There are some patches available that potentially solve the deadlock issue > but they need more testing. Perhaps this can be viewed as a request to perfect rxvt/cygwin pty handling. > Anyway, I'm concerned that defaulting to rxvt will just shuffle the bug > reports from "How do I get scroll bars?" to "Why doesn't my XYZ software > work right on CygWIN?" It may shift the bug reports in such a way that this long standing problem (along with the "clicking on the close button of an rxvt window does not properly kill the underlying shell" bug). I don't know, perhaps rxvt is not under the control of Cygwin developers... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/