kathmi / puttycyg

Automatically exported from code.google.com/p/puttycyg
0 stars 1 forks source link

After CTRL-C to terminate executing process command text is no longer visible on input #56

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Please read the FAQ and check existing issues before creating a new issue.

What steps will reproduce the problem?
1. Start puttycyg and start tailing a file using 'tail -f'. (Or just do some 
long running command that prints to the console)
2. Execute CTRL-C
3. You are returned to the command line. However, all future text that you 
enter from now on isn't echoed to the display. 

What is the expected result?  What happens instead?
Regardless of how an executing process was terminated, 
PutTTYcyg version: Any
Cygwin version: Any
Windows version: Windows 7, 64 bit

If you are experiencing performance issues, do you have a multi-core system
or multiple CPUs?
Yes
Do you have any firewall software installed?
Yes, but not applicable.
Please attach your PuTTY configuration.  Use this Windows command to create
putty.reg:
REG EXPORT HKEY_CURRENT_USER\Software\SimonTatham\PuTTY putty.reg
Doesn't depend on Putty configuration.

Please provide any additional information below.

Original issue reported on code.google.com by lenk...@gmail.com on 20 Jan 2011 at 6:55

GoogleCodeExporter commented 9 years ago
Does `stty reset` fix it?  If so, the program you've run has asked your 
terminal (PuTTYcyg) not to echo input characters and then neglected to reset 
the terminal before exiting, either because it was killed by an untrappable 
signal or because it neglected to correctly install a SIGINT handler (CTRL-c).

However, it does seem unlikely that tail is turning echo off (I don't know why 
it would need to do this).

Original comment by medgar123 on 21 Jan 2011 at 3:25