Message-ID: <4A1BD971.70808@cornell.edu>
Date: Tue, 26 May 2009 07:58:41 -0400
From: Ken Brown <kbrown@cornell.edu>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: emacs -nw keypad
References: <4A168F2B.4020805@cornell.edu> <2377ADF68DFE455199B53E97E5747E43@HEPNTLTIM3> <4A1B17FD.902@dronecode.org.uk>
In-Reply-To: <4A1B17FD.902@dronecode.org.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 5/25/2009 6:13 PM, Jon TURNEY wrote:
> I would have said that this could be same problem as in [1], an X server 
> bug, but then I would expect the problem to be seen both in "emacs -nw 
> in an xterm under X" and "emaacs under X"...

I'm not yet convinced that there's a bug.  The tpu-*.el files use the 
emacs variable 'window-system' to decide whether X windows is running. 
If I start emacs under X, that variable has the value x.  If I run emacs 
-nw in an xterm, the variable has the value nil.  If I run emacs under 
rxvt (without specifying -nw), I get the message

	Display :0 unavailable, simulating -nw

and again window-system has the value nil.  This strikes me as the 
correct behavior, consistent with the documentation of '-nw'.

I guess what's puzzling is why Tim doesn't have a problem with earlier 
versions of emacs.  Has something changed in how emacs interprets -nw? 
Or has tpu-edt changed?  Maybe Eli can clarify this.

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/