Ctrl+Break on Windows no longer leaves your terminal in a broken state.
What's wrong with this entry?
The eval interview session resets the terminal out of raw mode and clears its handlers on SIGBREAK, the Windows Ctrl+Break signal, as it already did for SIGINT, SIGTERM and SIGHUP. Without this, Ctrl+Break could leave the terminal in a broken state.
SIGBREAK
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Windows sandbox runtime now installs machine-wide
Both mention window
-
v2.1.239
PowerShell path checks distinguish a timeout from an error
Both mention window
-
v2.1.239
Windows pipe names no longer mangled by locale-specific lowercasing
Both mention window