X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: rolf <rff DOT news AT gmail DOT com>
Subject:  Re: Problems with cygwin bash shell under NT Emacs
Date:  Mon, 14 Jul 2008 12:32:00 +0200
Lines: 22
Message-ID:  <mykku57j.fsf@gmail.com>
References:  <od52ltz3 DOT fsf AT gmail DOT com> <g5ec5t$n90$2 AT ger DOT gmane DOT org>
Reply-To: rff DOT news AT gmail DOT com
Mime-Version:  1.0
Content-Type:  text/plain; charset=iso-8859-1
Content-Transfer-Encoding:  8bit
X-Attribution: rff
X-Jost-Rating: Highkey <6garf8$3aj$5 AT maamenchi DOT zrz DOT TU-Berlin DOT DE>
X-URL: http://www.fevr-media.com/~rff
User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/23.0.0 (windows-nt)
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

René wrote:

>> I'm running a native win32 version emacs.
> [snip]
>
> Then, why do you ask here? 
Couldn't it be, that the Cygwin port of python has something to do
with it?

> You should ask the NTEmacs list, tell them
> about your TERM and TERMCAP environment strings, those look like the
> real cause of the problem.
Thanks for the hint, I'll dig into TERM and TERMCAP

And, it seems I can't find a NTEmacs list alive. Is there one?

> Cygwin has emacs and XEmacs, both work fine.
I don't remember why, but my Emacs life started with NTEmacs and I
haven't bothered to change that. Maybe now is a good time....

--
Rolf


--
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/