{"version":"2.1.234","anchor":"terminal-is-restored-on-ctrl-break-on-windows","canonical_anchor":"terminal-is-restored-on-ctrl-break-on-windows","heading":"Terminal is restored on Ctrl+Break on Windows","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/terminal-is-restored-on-ctrl-break-on-windows","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Terminal is restored on Ctrl+Break on Windows\n\nCtrl+Break on Windows no longer leaves your terminal in a broken state.\n\n**What**\n\nThe 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.\n\n**Evidence**\n\n`SIGBREAK`\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}