This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Degrading tty behaviour
- To: cygwin at cygwin dot com
- Subject: Re: Degrading tty behaviour
- From: Andy Piper <andyp at bea dot com>
- Date: Wed, 25 Jul 2001 16:37:32 -0700
Corinna Vinschen <cygwin at cygwin dot com> wrote:
> Fine. What next? I told you I can't reproduce that. That's still true.
> What details can you provide except for "it doesn't work". What exactly
> doesn't work? You didn't even mention that!
My mistake. vim comes up but then any user input just makes it beep. For
instance Esc : q yields <beep> <beep> <beep>. I have to C-z and then kill
it to get out. The build of vim 5.7.x works fine.
> The next sentence in your mail begins with: "C-c behaviour is also
broken..."
> So your first sentence is not related to a non-functional C-c. So what
> is it what doesn't work?
I have reported this before. If you run a java program within bash and try
to C-c it, everything is fine. If you try to run a java program within a
shell-script within bash it is uninteruptible. C-z however does still work.
This is only true with CYGWIN=tty, without this everything is fine.
I only mention java because it is the one clearly reproducible problem from
a bunch of C-c issues I have when using CYGWIN=tty and bash.
Thanks
andy
--
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/