X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <4A1C9952.8040100@cornell.edu> Date: Tue, 26 May 2009 21:37:22 -0400 From: Ken Brown User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: emacs -nw keypad References: <4A168F2B DOT 4020805 AT cornell DOT edu> <2377ADF68DFE455199B53E97E5747E43 AT HEPNTLTIM3> <4A1B17FD DOT 902 AT dronecode DOT org DOT uk> <4A1BD971 DOT 70808 AT cornell DOT edu> <83bppfskbt DOT fsf AT gnu DOT org> <4A1C5831 DOT 6030008 AT cornell DOT edu> <99716858969849F89D65A4015B9948F7 AT HEPNTLTIM3> In-Reply-To: <99716858969849F89D65A4015B9948F7@HEPNTLTIM3> 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 On 5/26/2009 9:11 PM, Tim Adye wrote: > In Cygwin 1.5 xterm (TERM=xterm), with "emacs -q -nw" (or also with "-f > tpu-edt") I get > > ESC [ > 1 ; 2 4 2 ; 0 c ESC O q ESC O r ESC O s ESC > O t ESC O u ESC O v ESC O P l > > The initial "ESC [ > 1 ; 2 4 2 ; 0 c" is just the response from xterm, asked > for its version number (242). The "ESC O q" to "ESC O v" are the keypad > "123456", but somehow with numlock on (perhaps this is a feature of my > Exceed X-server). The "ESC O P l" is the "F1 l" at the end. > > Despite the differences, it looks like neither of us is getting any > interpretation of the keys. But this doesn't seem to have anything to do with recent versions of emacs. I just reverted to cygwin's emacs-21.2-13 (in cygwin-1.5) and repeated several of my tests (all except the one in rxvt), and the results were identical to those I reported before. I'll bet the problems you reported had nothing to do with updating emacs. Probably when you ran setup.exe to update emacs, other packages were updated at the same time, and changes in these are somehow responsible for the poor interaction between emacs and the terminal. I think you should be able to tell what other packages were updated by looking at /var/log/setup.log and/or /var/log/setup.log.full. Could terminfo be the culprit? Chuck, can you help? Ken -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/