Windows 10 Upgrade Bug Disabled Cntrl-C In Bash (infoworld.com)
An anonymous reader quotes InfoWorld:
A massive set of changes to the Windows Subsystem for Linux (WSL) was rolled into Windows Insider build 15002... If this is any hint, Microsoft's goal is nothing short of making it a credible alternative to other Linux distributions... Some of the fixes also implement functionality that wasn't available before to Linux apps in WSL, such as support for kernel memory overcommit and previously omitted network stack options. Other changes enhance integration between WSL and the rest of Windows...
[O]ne major issue in build 15002 is that Ctrl-C in a Bash session no longer works. Microsoft provided an uncommon level of detail for how this bug crept in, saying it had to do with synchronization between the Windows and Bash development teams. The next Insider build should have a fix. But for people doing serious work with Linux command-line apps, not having Ctrl-C is a little like driving a car when only the front brakes work.
[O]ne major issue in build 15002 is that Ctrl-C in a Bash session no longer works. Microsoft provided an uncommon level of detail for how this bug crept in, saying it had to do with synchronization between the Windows and Bash development teams. The next Insider build should have a fix. But for people doing serious work with Linux command-line apps, not having Ctrl-C is a little like driving a car when only the front brakes work.
Computers running OSX have substantial developer mindshare. Microsoft wants those developers using Windows PCs. Putting WSL/Bash on Windows so that it's a credible alternative to the 'nix tools available on OSX gives those developers one less reason to avoid using a Windows based OS.
You know, some of us use windows since it's quite client facing. This might blow your mind. Anything either side can do to bridge the gap of best of both worlds is a good thing.
"Old man yells at systemd"
WSL is better than cygwin. It is a lot faster and it has apt-get instead of that dreadful install wizard that cygwin has.
However, the console in windows is stuck in the 80's. It is the same DOS command prompt that we saw in windows 3.1. The terminal emulators in linux or macOS support multiple tabs, text selection that reaches the end of the line instead of a rectangular shape, split panes, your default directory is your home directory.
Now someone will raise their hand and say "PowerShell ISE". It looks promising, but at this point it is unusable because console programs cannot read input in PowerShell ISE
Until they have a console from this century, WSL is worth using only when you don't have linux or macOS available.