X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <4A1AEC57.3040006@cornell.edu> Date: Mon, 25 May 2009 15:07:03 -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> In-Reply-To: <2377ADF68DFE455199B53E97E5747E43@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/25/2009 2:23 PM, Tim Adye wrote: > I have however found one problem with this experimental release 23.0.92-2: > when I run it in no-window mode (emacs -nw) in an xterm (or rxvt), the > keypad keys do not seem to be defined or mapped to emacs functions. I use > tpu-edt mode, which relies on those keys. It worked fine in emacs 21.2.1 (I > just tested on another system) and 23.0.92-2 works fine in window mode > (without -nw). I don't know the answer, but I can think of a couple things you could try. First, take a look at the news file for emacs 22. (C-u C-h C-n, then enter 22 when you're prompted for the version.) Search for 'keypad', and you'll find a discussion of a new keypad setup package. I don't use it myself, so I don't know if it's relevant. A second possibility is to use the version of emacs compiled without X support (/usr/bin/emacs-nox.exe) to see if that works better than emacs -nw (which is really emacs-X11.exe -nw after you unwind the symbolic links). If neither of these helps, try asking for help on emacs-devel or help-gnu-emacs. A lot has changed since emacs 21.2. > I am a bit concerned that we are jumping ahead to the bleeding edge. That's > fine for an experimental release like this, but a bit worrying if this is to > become the default Cygwin release. Is there a particular problem with 22.3 > that forced you to jump forward? My original plan was to build emacs 22.3 for cygwin 1.5, leaving the bleeding edge for people who were testing cygwin 1.7. Unfortunately, the standard method for making cygwin packages (cygport) didn't work with emacs 22.3, so it would have been very time consuming to package it. I decided it wasn't worth the effort since emacs 23 seems to be reasonably stable and will probably be released in the not-too-distant future. 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/