Hazardous key repeats across tabs #6414

Closed
opened 2026-01-31 00:37:56 +00:00 by claunia · 3 comments
Owner

Originally created by @gitfool on GitHub (Feb 13, 2020).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 0.9.433.0

Steps to reproduce

  • Open multiple tabs to Linux shells, either WSL or ssh to Linux remotes
  • Press and hold down ctrl+d to close the currently active shell

Expected behavior

  • Only the active shell / tab should close

Actual behavior

  • All shells / tabs close in quick succession

Of course it might be unreasonable for me to expect the behavior I describe above, but I've been bitten a few times already where just pressing what I thought was a normal ctrl+d key sequence must've lingered a fraction too long, thereby "repeated" and accidentally closed another shell / tab I didn't intend to.

Originally created by @gitfool on GitHub (Feb 13, 2020). # Environment ```none Windows build number: 10.0.18363.0 Windows Terminal version (if applicable): 0.9.433.0 ``` # Steps to reproduce - Open multiple tabs to Linux shells, either WSL or ssh to Linux remotes - Press and hold down `ctrl+d` to close the currently active shell # Expected behavior - Only the active shell / tab should close # Actual behavior - All shells / tabs close in quick succession Of course it might be unreasonable for me to _expect_ the behavior I describe above, but I've been bitten a few times already where just pressing what I thought was a normal `ctrl+d` key sequence must've lingered a fraction too long, thereby "repeated" and accidentally closed another shell / tab I didn't intend to.
claunia added the Needs-Tag-FixResolution-Won't-Fix labels 2026-01-31 00:37:56 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Feb 13, 2020):

Interesting. I'm not sure how we comport this with "I want my input to instantly and immediately go to the active terminal." hmm

@DHowett-MSFT commented on GitHub (Feb 13, 2020): Interesting. I'm not sure how we comport this with "I want my input to instantly and immediately go to the active terminal." _hmm_
Author
Owner

@gitfool commented on GitHub (Feb 13, 2020):

Understood. I resisted logging an issue for a while, but it recently happened while I was mid "deploy" in another shell / tab, which needless to say was not good. 😱

@gitfool commented on GitHub (Feb 13, 2020): Understood. I resisted logging an issue for a while, but it recently happened while I was mid "deploy" in another shell / tab, which needless to say was not good. 😱
Author
Owner

@DHowett-MSFT commented on GitHub (Feb 14, 2020):

Tentatively, I'm going to close this one- I appreciate that it's bitten you, but we're optimizing for input fidelity and time-to-response, and this may just have to be fallout for that. Terminal will -- or, should! -- respect your OS-wide key repeat delay. I know that's not an amazing way to fix this, but I can't find any prior art on suppressing control characters for something like this.

@DHowett-MSFT commented on GitHub (Feb 14, 2020): Tentatively, I'm going to close this one- I appreciate that it's bitten you, but we're optimizing for input fidelity and time-to-response, and this may just have to be fallout for that. Terminal will -- or, should! -- respect your OS-wide key repeat delay. I know that's not an amazing way to fix this, but I can't find any prior art on suppressing control characters for something like this.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6414