Re: ctrl-c swallowed

["Gareth Pearce" <tilps at hotmail dot com>]

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