X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4E0C62D6.3060901@cornell.edu> Date: Thu, 30 Jun 2011 07:49:42 -0400 From: Ken Brown User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Emacs and removal of CYGWIN=tty References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit 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 On 6/30/2011 3:58 AM, Lars Bjørndal wrote: > I've heard that the value of the CYGWIN environment variable 'tty' will > be unsupported for the next release of cygwin. I use emacs a lot from within > cygwin, and if not CYTWIN=tty is set prior to starting bash, the control-c > character outputs control-g. C-c, c-x is therefore wrongly interpreted > by emacs. Is there other ways to get emacs works as expected, if the > variable is removed? The problem only occurs in a Windows console, such as the one you get by using the Cygwin desktop shortcut. Use a different terminal emulator, such as mintty, instead. Ken -- 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