Running 'cmd.exe' in window (as called from bash') doesn't protect against ctrl-c

[GoogleCodeExporter]

What steps will reproduce the problem?
1. bring up a standard Cygwin-window w/bash.  enter cmd.exe and press ctrl-c
Notice how it simplly gives you another prompt within cmd.exe. -- i.e.
cmd.exe catches control-c and to exit back to bash, type exit.
2. Now do the same in a mintty window.  Have it start bash, just as
a cygwin shortcut does.  Then run cmd.exe.  Then press ctrl-c.  The CTRL-c
isn't caught by cmd.exe.  Instead it is terminated. and the user ends up
back in bash.
3.

What is the expected output? What do you see instead?
expect cmd.exe to catch control-c as in a cygwin-called bash

What version of the product are you using? On what operating system?
v4.4 of mintty (latest available on cygwin site...I'll have to try newer
version), and using cygwin 1.5 and winXP-SP3).

I *don't* regard this as a high-priority bug -- I don't use cmd.exe that
often.  It's just a '_difference_' I noticed between mintty and a standard
'windows' window running bash.  It's a bit annoying -- and can take some
getting used to -- but if I really need cmd.exe, I could always use an
old-style Windows-based window.  It's *rare* I use cmd.exe except to test
Windows-compatible pathnames and invocations.

Original issue reported on code.google.com by min...@tlinx.org on 6 Nov 2009 at 6:58

• Merged into: #56

[GoogleCodeExporter]

You'll also find that cmd.exe history won't work in mintty, and cursor 
positioning is
wonky too. Basically, cmd.exe isn't supported because it's designed to run in a
Windows console rather than a Unix terminal. See issue 56 for more problems with
native console programs and lots of half-baked ideas on how the issue could be 
addressed.

Original comment by andy.koppe on 6 Nov 2009 at 7:18

• Changed state: Duplicate