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.
But for people doing serious work with Linux command-line apps
...we use a Linux operating system.
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.
It isn't an "upgrade bug" as the upgrade isn't slated for release for months.The build in question has only been released to the fast ring for Insider testing. In other words, it's only been given to those on the extreme bleeding edgeof Windows testing.Is Slashdot going to start posting articles for every minor issue in Chrome canary releases also?
As their revenue dwindles let this be a lesson.
Microsoft revenue has grown in a more or less linear fashion since the 90s. Doesn't stop idiots from announcing their imminent doom for over 25 years.
lucm, indeed.
They literally broke break.
Do not look into laser with remaining eye.
People who decided to use \ as path separator?
Slashdot, fix the reply notifications... You won't get away with it...