Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-Id: <4.3.2.7.2.20010724151409.01766098@san-francisco.beasys.com>
Date: Tue, 24 Jul 2001 15:28:42 -0700
To: cygwin@cygwin.com
From: Andy Piper <andyp@bea.com>
Subject: Re: Degrading tty behaviour 
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed


Corinna Vinschen wrote:
 > Unfortunately your mail sounds just like ranting without providing
 > any detail, so I will trash it.

Why do you assume this? What was it about my mail that made you think this? 
I would genuinely like to know. The posting certainly wasn't meant as a 
rant and its this sort of repsonse that makes it difficult to work with the 
cygwin developers.

 > I'm using vim-5.8 all day long and I'm using CYGWIN=tty setting from
 > a ssh connection to the NT box. I have also just tried it with CYGWIN=tty
 > from a cmd window. Works for me (except from mutt which I can reproduce).

And I cannot use vim-5.8 because of this problem. Removing tty from my 
CYGWIN environment fixes it - which seems pretty compelling evidence to me. 
This is true on both NT and W2K. Note that it *does* work from a cmd 
window, it *doesn't* work from a cygwin bash window. Surely using a ssh 
connection to the NT box is not a reasonable test given that it is 
shell/window dependant?

What more details would you like to see? Did you try C-c'ing a java process 
from within bash also?

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/