Undo function for closing tabs and windows. #12553

Closed
opened 2026-01-31 03:18:37 +00:00 by claunia · 5 comments
Owner

Originally created by @mingwandroid on GitHub (Feb 13, 2021).

Undo feature for closing tabs and windows.

Proposed technical implementation details (optional)

Originally created by @mingwandroid on GitHub (Feb 13, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Undo feature for closing tabs and windows. <!-- Sometimes we make mistakes, sometimes I close tabs or windows with processes I very much didn't mean to kill. I wonder if it'd be possible for the actual termination of the process(es) to be able to be deferred for a small amount of time (say 3 to 10 seconds) via an option. Then a specific key combo (or just undo?) could be used to 'recreate' (probably this would be an un-hide operation under the hood?) the tab or window. --> # Proposed technical implementation details (optional) <!-- If I close a window or tab then quickly change my mind, I'd like to be able to press a key combo to 'undo' this action. I don't know how easy this would be to implement but I feel it would be a great addition to an already great project. -->
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 03:18:37 +00:00
Author
Owner

@KalleOlaviNiemitalo commented on GitHub (Feb 14, 2021):

There is a long discussion about similar features in https://github.com/microsoft/terminal/issues/961.

@KalleOlaviNiemitalo commented on GitHub (Feb 14, 2021): There is a long discussion about similar features in <https://github.com/microsoft/terminal/issues/961>.
Author
Owner

@mingwandroid commented on GitHub (Feb 15, 2021):

OK, that issue talks about "restoring" state which is very complicated. My idea is to side-step this by not actually killing anything during this grace-period. I will add the idea over there though if you think them related. I wouldn't personally touch "restoring" state as something I would want to implement.

@mingwandroid commented on GitHub (Feb 15, 2021): OK, that issue talks about "restoring" state which is very complicated. My idea is to side-step this by not actually killing anything during this grace-period. I will add the idea over there though if you think them related. I wouldn't personally touch "restoring" state as something I would want to implement.
Author
Owner

@Don-Vito commented on GitHub (Feb 15, 2021):

@mingwandroid, @KalleOlaviNiemitalo - I think you are off by one 😄. Please see https://github.com/microsoft/terminal/issues/960

@Don-Vito commented on GitHub (Feb 15, 2021): @mingwandroid, @KalleOlaviNiemitalo - I think you are off by one :smile:. Please see https://github.com/microsoft/terminal/issues/960
Author
Owner

@zadjii-msft commented on GitHub (Feb 16, 2021):

Okay yea, this is definitely #960. The set of #960, #961 and #766 are all super closely related, so I don't fault anyone for getting them mixed up 😄

/dup #960

@zadjii-msft commented on GitHub (Feb 16, 2021): Okay yea, this is definitely #960. The set of #960, #961 and #766 are all super closely related, so I don't fault anyone for getting them mixed up 😄 /dup #960
Author
Owner

@ghost commented on GitHub (Feb 16, 2021):

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 (Feb 16, 2021): 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#12553