[PR #5472] Re-enable Ctrl-C if the application that spawned us disabled it #26344

Closed
opened 2026-01-31 09:15:28 +00:00 by claunia · 0 comments
Owner

Original Pull Request: https://github.com/microsoft/terminal/pull/5472

State: closed
Merged: Yes


If Terminal is spawned by a shortcut that requests that it run in a new process group
while attached to a console session, that request is nonsense. That request will, however,
cause WT to start with Ctrl-C disabled. This wouldn't matter, because it's a Windows-subsystem
application. Unfortunately, that state is heritable. In short, if you start WT using cmd in
a weird way, ^C stops working inside the terminal. Mad.

Fixes #5460.

**Original Pull Request:** https://github.com/microsoft/terminal/pull/5472 **State:** closed **Merged:** Yes --- If Terminal is spawned by a shortcut that requests that it run in a new process group while attached to a console session, that request is nonsense. That request will, however, cause WT to start with Ctrl-C disabled. This wouldn't matter, because it's a Windows-subsystem application. Unfortunately, that state is heritable. In short, if you start WT using cmd in a weird way, ^C stops working _inside_ the terminal. Mad. Fixes #5460.
claunia added the pull-request label 2026-01-31 09:15:28 +00:00
Sign in to join this conversation.
No Label pull-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#26344