Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Originating-IP: [202.7.175.77]
From: "Gareth Pearce" <tilps AT hotmail DOT com>
To: <cygwin AT cygwin DOT com>
Subject: nano Ctrl-C difficulties...
Date: Fri, 2 Aug 2002 23:25:45 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <OE57fiBFoM1sGXUixgn0000e30f@hotmail.com>
X-OriginalArrivalTime: 02 Aug 2002 13:26:01.0181 (UTC) FILETIME=[24E3D8D0:01C23A28]

Okay - attempting to dig my way into solving my nano ctrl-c problems...
Some external help along with my own research has led me to the following
data.
problem seems independent of windows version (problem occurs on both 2k and
ME)
problem occurs in cmd/command/bash/tcsh
problem doesnt occur in rxvt/xterm
problem disapears with CYGWIN=tty.

Which brings up the question...
What should nano be doing in order to work without tty, (if at all possible)
since not forcing use of tty would be preferable. (and answering this
problem might solve my OSF/1 version of this problem too).  Or is answering
this question too non-cygwin related...

Gareth

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/