Issue: In Windows 10 Insider build 15002, when running Bash.exe, CTRL + chords are not being correctly handled by the Windows Console.
Effect: Users will be unable to terminate Linux apps using CTRL + C, or background running tasks using CTRL + Z, etc. When CTRL + C is hit in Bash, a ‘c’ is displayed in the bash console.
Work-Around(s): Until fixed:
stty intr \^k
Scope: This issue only affects Bash sessions and does not prevent CTRL + C, etc. in other console apps or shells (i.e. Cmd or PowerShell).
For more information on this release, including the many other fixes it DOES include, be sure to read the build 15002 Release Notes.
We apologize for this annoying issue. A fix has been checked-in and will be released ASAP into an up-coming Insiders build.
Still works like a charm under wsl-terminal https://github.com/goreliu/wsl-terminal ;-)
Thank you. It'll be great to have that fix in the system. For now, I've mapped CTRL-C to CTRL-P; which is how PR1MOS computers at my university handled 'interrupt' 35 years ago. Can't beat nostalgia.
A fellow Surrey graduate -- small world!
@benhillis Do we have a scheduled release date for this fix? Thanks!
@seancorfield No, we generally don't get notice for when the next insider build gets flighted. And the team here doesn't control it. Ask @donasarkar on twitter maybe.
I'm hoping next week's build has the fix.