X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org X-RAL-MFrom: X-RAL-Connect: From: "Tim Adye" To: "'Ken Brown'" , References: <4A168F2B DOT 4020805 AT cornell DOT edu> <2377ADF68DFE455199B53E97E5747E43 AT HEPNTLTIM3> <4A1AEC57 DOT 3040006 AT cornell DOT edu> Subject: RE: emacs -nw keypad Date: Tue, 26 May 2009 01:34:55 +0100 Keywords: Addressed to T DOT J DOT Adye AT rl DOT ac DOT uk Message-ID: <5C971BF50E964C8DBBC973FA3C61380A@HEPNTLTIM3> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <4A1AEC57.3040006@cornell.edu> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Ken, > 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. I tried changing those settings without much luck. Anyway I don't think those settings can help, since they were already there in 22.2.1, which doesn't have this problem. > 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). Same problem with emacs-nox. > If neither of these helps, try asking for help on emacs-devel > or help-gnu-emacs. A lot has changed since emacs 21.2. On Linux there's no problem with emacs 22.2.1 at least. > 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. Ah, OK. It does mean one can't easily tell if the problem is Cygwin-specific. Normally I can check a Linux distribution with a similar version. > Out of curiosity, is there some reason why you need to use > the -nw switch when you run emacs? I don't use it all the time, but it's a lot quicker to run emacs -nw in an rxvt than starting an X-server just for a quick edit - if I don't happen to have the X-server running already. Of course another option is the Windows version of emacs, so it's not essential, just handy. Thanks, Tim. =========================== cut here ============================ Tim Adye T DOT J DOT Adye AT rl DOT ac DOT uk http://hepunx.rl.ac.uk/~adye Atlas/BaBar Groups, Particle Physics Dept, Rutherford Appleton Lab -- 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/