X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,SPF_NEUTRAL,TW_RX,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <500829BD.3010108@cs.utoronto.ca> Date: Thu, 19 Jul 2012 11:37:33 -0400 From: Ryan Johnson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: "cygwin AT cygwin DOT com" Subject: mintty and modifier keys Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Hi all (mostly Andy), I notice that mintty 1.1 handles certain key combinations differently than xterm: ctrl+enter produces 0x1e (RS) vs. CR in xterm alt+enter produces ESC CR vs. nothing at all in xterm ctrl+shift+ emits the unicode C2 control codepoints (0xc281 through 0xc29a); xterm emits the C0 control value as if shift were unpressed. So, two questions: 1. Is there a particular reason for this behavior? Perhaps rxvt or some other non-xterm terminal emulator does it? 2. Is there documentation somewhere of what convention mintty follows for the various special cases? (these questions are partly triggered by frustration at shift+enter not working, which lead to me finding a reasonably sane proposal to fix these kinds of terminal woes [1]; I was surprised to find that mintty can already distinguish some key presses that xterm can't) [1] www.leonerd.org.uk/hacks/fixterms/ Thanks, Ryan -- 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