delorie.com/archives/browse.cgi | search |
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: | [150.101.116.22] |
X-Originating-Email: | [tilps AT hotmail DOT com] |
From: | "Gareth Pearce" <tilps AT hotmail DOT com> |
To: | =?iso-8859-1?Q?Anders_Lind=E9n?= <cygwin AT cardioid DOT se>, <cygwin AT cygwin DOT com> |
References: | <003a01c36fee$7ba18b70$ddb470d5 AT gotia> <3F527055 DOT 9C5FD822 AT dessent DOT net> <20030831232934 DOT GA13584 AT redhat DOT com> <3F528B30 DOT 39E99A7B AT dessent DOT net> <001501c37051$ce4adb20$d4b470d5 AT gotia> |
Subject: | Re: ctrl-c swallowed |
Date: | Mon, 1 Sep 2003 16:43:28 +1000 |
MIME-Version: | 1.0 |
X-Priority: | 3 |
X-MSMail-Priority: | Normal |
X-MimeOLE: | Produced By Microsoft MimeOLE V6.00.2800.1165 |
Message-ID: | <BAY2-DAV37qGa9F82he0000f85b@hotmail.com> |
X-OriginalArrivalTime: | 01 Sep 2003 06:43:37.0003 (UTC) FILETIME=[5F01E7B0:01C37054] |
> > > Christopher Faylor wrote: > > > > > >I don't know if this is the "officially correct" answer or not, but I > > > >find that ^C doesn't work right with some programs when run from > > > >CMD.EXE unless I have the "tty" flag added to the CYGWIN environment > > > >variable. The users' guide has a section on how to do this, I'm sure. > > > > > > CTRL-C is designed to work correctly with cygwin applications in either > > > tty or notty mode. Please don't spread FUD if you aren't providing > > > details. > > > > In pico, without CYGWIN=tty, pressing ^C does nothing. With CYGWIN=tty, > > it works as it's supposed to (displays the current position.) That's > > all, just my observation. > > > Yeah! Thats correct! For some reason, if pico (or nano) is runned with CYGWIN=tty, > it will make the terminal go crazy when it is terminating. The terminal will not display any output, just consume input. > "stty sane" or "reset" did not alter that behaviour... I find this behaviour if i set the cygwin=tty variable after having started the bash prompt. Setting it before (ie adding it to the system environment variables) has no problems. ctrl-C and (i think) ctrl-T not working in nano are the only reasons i set cygwin=tty. Gareth > > > > > Brian > > > > -- > > 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/ > > > > > -- > 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/ > > -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |