shell loses "stty echo" state

Charles Wilson cwilson@ece.gatech.edu
Fri Dec 29 12:01:00 GMT 2000


Ashok Vadekar wrote:
> 
> I installed 1.1.7 on a Win2000 (Professional) machine and have noticed the
> following problem.  After running vi (vim) or less, the console is returned
> in a state where shell input is not echoed back to the display.  If I reenter
> vi, keyboard input is show (ie. typing ":q" shows ":q" on the bottom line).
> 
> Running stty before and after the problem occurs show that -echo has been
> set.  However, stty fails when I try "stty echo" to undo the change.  Actually
> it seems to fail for any input I try.
> 
> I would guess that the problem is in closing a curses session with the console,
> since commands that only perform simple console IO do not cause the problem.

Nope.  The vim distributed with cygwin does NOT use the curses library. 
It uses termcap only.  So don't blame ncurses.

BTW, I don't see this problem and I'm on Win2K (but haven't upgraded to
1.1.7; I'm still using 1.1.6)

--Chuck

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple



More information about the Cygwin mailing list