X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 	tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <27114208.post@talk.nabble.com>
Date: Mon, 11 Jan 2010 09:25:37 -0800 (PST)
From: aputerguy <nabble AT kosowsky DOT org>
To: cygwin AT cygwin DOT com
Subject: ntEmacs has trouble with cygwin terminal...
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


Here is the situation:

Running from a cygwin 1.7 bash terminal:
$ emacs -nw
<opens up terminal-based emacs session in current cygwin terminal>

$emacsclient -nw
*ERROR*: Not using an ASCII terminal now; cannot make a new ASCII frame

$echo $TERM
cygwin

Running from within screen within cygwin:
$ emacs -nw
emacs: standard input is not a tty

$ emacsclient -nw
*ERROR*: Not using an ASCII terminal now; cannot make a new ASCII frame

$ echo $TERM
screen

SO...
1. Why is emacsclient -nw fails within a cygwin terminal while emacs -nw
works?
2. Why do *neither* of them work within screen? 

NOTE: When I posted this to the emacs-windows mailing list, their basic
response was that this is an incompatibility between ntEmacs and cygwin
terminal. Specifically,
"...the native build of Emacs and Cygwin tools are subtly
incompatible in the ways they deal with the terminal.  Mixing them is
asking for trouble.  If you want everything to work as expected,
either don't run NTEmacs from Cygwin programs, or use the Cygwin build
of Emacs."

Perhaps that is the best and final answer -- but I wanted to just make sure
that the cygwin developers were aware of this in case there is an easy fix
on the cygwin side.

Note though that there are good reasons why I use ntEmacs and not cygwin
Emacs -- so the best answer for me is not just to switch to cygwin emacs...
-- 
View this message in context: http://old.nabble.com/ntEmacs-has-trouble-with-cygwin-terminal...-tp27114208p27114208.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple