From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30268 invoked by alias); 22 May 2011 21:19:23 -0000 Received: (qmail 30260 invoked by uid 22791); 22 May 2011 21:19:23 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_NONE,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org Received: from nm14.bullet.mail.bf1.yahoo.com (HELO nm14.bullet.mail.bf1.yahoo.com) (98.139.212.173) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Sun, 22 May 2011 21:19:08 +0000 Received: from [98.139.212.150] by nm14.bullet.mail.bf1.yahoo.com with NNFMP; 22 May 2011 21:19:07 -0000 Received: from [98.139.213.5] by tm7.bullet.mail.bf1.yahoo.com with NNFMP; 22 May 2011 21:19:07 -0000 Received: from [127.0.0.1] by smtp105.mail.bf1.yahoo.com with NNFMP; 22 May 2011 21:19:07 -0000 Received: from cgf.cx (cgf@173.48.46.160 with login) by smtp105.mail.bf1.yahoo.com with SMTP; 22 May 2011 14:19:07 -0700 PDT X-Yahoo-SMTP: jenXL62swBAWhMTL3wnej93oaS0ClBQOAKs8jbEbx_o- Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 3142642804C for ; Sun, 22 May 2011 17:19:07 -0400 (EDT) Date: Sun, 22 May 2011 21:19:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: CYGWIN=tty round 2 Message-ID: <20110522211906.GA13428@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-05/txt/msg00325.txt.bz2 I don't think we saw anyone step forward with a valid reason why they needed to use CYGWIN=tty over something like "mintty". I've summarized the thread where Corinna asked why people used CYGWIN=tty over CYGWIN=notty below. I don't see any showstoppers here so unless people can provide specific examples of how this change would cause hardwhip, we'll be removing CYGWIN=tty in a snapshot near you soon. Summary: 0) There was some confusion over what Corinna meant by CYGWIN=notty. Response: Corinna thought (as did I) that people would understand that CYGWIN=notty is the default. It's what you get if you haven't added "tty" to the CYGWIN environment variable. And, if you don't know what any of that means then this whole discussion is not something that you have to worry about. 1) People thought that because CYGWIN=tty was mentioned in an example in the documentation, it was actually a recommendation. Response: It was not a recommendation (if it was it would have been the default). It has been removed from the documentation. 2) screen needs CYGWIN=tty for reattach to work. Response: Use "mintty". Or, possibly proposed changes for 9 below will cause reattach to work with screen. 3) emacs requires CYGWIN=tty for CTRL-C to work. Response: Use "mintty". Long-term possibly get CTRL-C working with the cygwin console. 4) sshd requires CYGWIN=tty. Response: Pure unadulterated rumor. This was never the case unless you needed to inexplicably slow down sshd for some unknown reason. 5) brltty might need it. Response: brltty doesn't need it. 6) "It made something I cared about work properly and four M$ operating systems later..." Response: Use mintty or provide a specific example of failure. 7) There's a bug in Cygwin's console handling. Response: We'll (eventually) fix the bug. 8) "Not a power user and don't understand the question" Response: Don't worry about it then. You probably aren't using the setting. 9) With CYGWIN=tty, each console window gets its own /dev/ttyN. For console windows everything gets /dev/console and, so, there is no way to distinguish between console windows. Response: Cygwin will be changed to cause each console window to have its own unique /dev/consN numbering, similar to /dev/ttyN. 10) The non-cygwin application "jam" inexplicably seems to require it for proper operation. Response: One workaround was suggested when dealing with console mode but it seems that mintty would also cause jam to work ok as well. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple