X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: Who's using "CYGWIN=tty" and why? Date: Mon, 09 May 2011 12:32:02 -0400 Lines: 21 Message-ID: <415gs6tmaaqmocs479tgkq1v5qs8mlchk6@4ax.com> References: <20110509161028 DOT GJ27739 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 > Chris and I are wondering how many people are using the Windows console > as local console window in CYGWIN=tty mode and why. /usr/share/doc/screen/README.Cygwin says: "In a DOS console, screen works, but in order to be able to reattach detached sessions, you must set "tty" in the CYGWIN environment variable.... If you use screen in a DOS console without CYGWIN=tty, you will be able to detach sessions, but reattaching to them later is likely to fail. Then you'll have to use 'screen -wipe' to clear out your old unusable sessions, and you may have to manually kill their child processes." So it seems that screen users who are still using a DOS console need CYGWIN=tty. I have no idea how many such people there are. If CYGWIN=tty is going away, then we could simply tell screen users that the DOS console is no longer supported in screen, since reattaching there is likely to fail. Andrew. -- 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