Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle for merging or moving a terminal window #4133

Closed
srv-code opened this issue Jan 7, 2020 · 4 comments
Closed

Handle for merging or moving a terminal window #4133

srv-code opened this issue Jan 7, 2020 · 4 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@srv-code
Copy link

srv-code commented 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).
@srv-code srv-code added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jan 7, 2020
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jan 7, 2020
@zadjii-msft
Copy link
Member

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 Add support for tab tearoff and tab merge #1256
  2. This one's being tracked as a part of Scenario: Add support for panes  #1000, but doesn't have it's own issue, it's only tracked as this Add support for tab reordering #443 (comment)
  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 Add support for tab tearoff and tab merge #1256.

@srv-code
Copy link
Author

srv-code commented Jan 7, 2020

Yes. Its #1256.

@DHowett-MSFT
Copy link
Contributor

/dup #1256.

@ghost
Copy link

ghost commented 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 ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jan 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants