Handle for merging or moving a terminal window #5805

Closed
opened 2026-01-31 00:22:16 +00:00 by claunia · 4 comments
Owner

Originally created by @srv-code on GitHub (Jan 7, 2020).

Please provide a handle to:

  1. Move a window opened in either vertical or horizontal split to a new window as a tab.
  2. Move a tab inside another tab in either vertical or horizontal split (depending upon the dropping region, bottom region suggests to split horizontally and side-wise dropping suggests vertical split similar to MS Visual Studio window re-arrangement mechanism).
  3. Interchange horizontal and vertical split modes.
  4. Move a window in either of the split modes or tab to a new app window (in another app instance).
Originally created by @srv-code on GitHub (Jan 7, 2020). Please provide a handle to: 1. Move a window opened in either vertical or horizontal split to a new window as a tab. 2. Move a tab inside another tab in either vertical or horizontal split (depending upon the dropping region, bottom region suggests to split horizontally and side-wise dropping suggests vertical split similar to MS Visual Studio window re-arrangement mechanism). 3. Interchange horizontal and vertical split modes. 4. Move a window in either of the split modes or tab to a new app window (in another app instance).
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 00:22:16 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Jan 7, 2020):

As I mentioned in #3386:

Please don't file giant issues with multiple issues reported like this one. It makes triaging and tracking the individual component issues much harder.

  1. Is this "drag a pane out to a new window"? That's probably not possible with our current architecture, but something that could be possible after #1256
  2. This one's being tracked as a part of #1000, but doesn't have it's own issue, it's only tracked as this https://github.com/microsoft/terminal/issues/443#issuecomment-519077162
  3. This doesn't have it's own issue yet, a new issue should be filed to discuss this feature.
  4. Yea this definitely falls under the bucket of #1256.
@zadjii-msft commented on GitHub (Jan 7, 2020): As I mentioned in #3386: > Please don't file giant issues with multiple issues reported like this one. It makes triaging and tracking the individual component issues much harder. 1. Is this "drag a pane out to a new window"? That's probably not possible with our current architecture, but something that could be possible after #1256 2. This one's being tracked as a part of #1000, but doesn't have it's own issue, it's only tracked as this https://github.com/microsoft/terminal/issues/443#issuecomment-519077162 3. This doesn't have it's own issue yet, a new issue should be filed to discuss this feature. 4. Yea this definitely falls under the bucket of #1256.
Author
Owner

@srv-code commented on GitHub (Jan 7, 2020):

Yes. Its #1256.

@srv-code commented on GitHub (Jan 7, 2020): Yes. Its [#1256](https://github.com/microsoft/terminal/issues/1256).
Author
Owner

@DHowett-MSFT commented on GitHub (Jan 7, 2020):

/dup #1256.

@DHowett-MSFT commented on GitHub (Jan 7, 2020): /dup #1256.
Author
Owner

@ghost commented on GitHub (Jan 7, 2020):

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 7, 2020): 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#5805