[feature request] Command / tab context menu item "Reset a tab" #16489

Closed
opened 2026-01-31 05:13:42 +00:00 by claunia · 2 comments
Owner

Originally created by @vadimkantorov on GitHub (Jan 24, 2022).

When ssh hangs in WSLv1 (usually because of network issues or after laptop sleep / hibernate), somehow it doesn't react to any Ctrl+C, Ctrl+Z. Then it's impossible to kill the ssh process, and it can take a few minutes for it to bail out by itself.

Current workaround: kill the whole tab (as it's impossible to kill the current process), open a new tab

Feature request: "reset a tab" command that will restart the tab (and preserve the tab's place in the tab bar).

Alternative feature request: somehow detecting the current process in the bash session and providing a command to kill it

Originally created by @vadimkantorov on GitHub (Jan 24, 2022). When ssh hangs in WSLv1 (usually because of network issues or after laptop sleep / hibernate), somehow it doesn't react to any Ctrl+C, Ctrl+Z. Then it's impossible to kill the ssh process, and it can take a few minutes for it to bail out by itself. Current workaround: kill the whole tab (as it's impossible to kill the current process), open a new tab Feature request: "reset a tab" command that will restart the tab (and preserve the tab's place in the tab bar). Alternative feature request: somehow detecting the current process in the bash session and providing a command to kill it
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 05:13:42 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Jan 24, 2022):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #3726 for more discussion.

/dup #3726

@zadjii-msft commented on GitHub (Jan 24, 2022): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #3726 for more discussion. /dup #3726
Author
Owner

@ghost commented on GitHub (Jan 24, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jan 24, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16489