X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <4A1B0492.4010501@cornell.edu> Date: Mon, 25 May 2009 16:50:26 -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 just had another thought. I wonder if it's tpu-edt that's changed. If you look at the current tpu-edt.el (in /usr/share/emacs/23.0.92/lisp/emulation), it says: > ;; TPU-edt works with X-windows. This is accomplished through a TPU-edt > ;; X key map. But, according to 'man emacs', the purpose of the -nw switch is to "Tell Emacs not to use its special interface to X." So maybe you're trying to do two contradictory things, and maybe it was different with older versions of tpu-edt. I'm just speculating. Out of curiosity, is there some reason why you need to use the -nw switch when you run emacs? 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/