This is the mail archive of the
mailing list for the Cygwin project.
Re: ctrl-c swallowed
- From: Anders Lindén <cygwin at cardioid dot se>
- To: <cygwin at cygwin dot com>
- Date: Mon, 1 Sep 2003 08:25:15 +0200
- Subject: Re: ctrl-c swallowed
- References: <003a01c36fee$7ba18b70$ddb470d5@gotia> <3F527055.9C5FD822@dessent.net> <20030831232934.GA13584@redhat.com> <3F528B30.39E99A7B@dessent.net>
----- Original Message -----
From: "Brian Dessent" <email@example.com>
Sent: Monday, September 01, 2003 1:56 AM
Subject: Re: ctrl-c swallowed
> 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...
> 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