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

Ability to drag tabs out and move them to a new instance #15227

Closed
sur1v opened this issue Apr 23, 2023 · 2 comments
Closed

Ability to drag tabs out and move them to a new instance #15227

sur1v opened this issue Apr 23, 2023 · 2 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

@sur1v
Copy link

sur1v commented Apr 23, 2023

Hey thanks for this product, I'm enjoying it a lot. Below affirmations based on version 1.16.10262.0.

Description of the new feature/enhancement

I would like to suggest the addition of a new feature in Windows Terminal that would allow users to drag a terminal tab out of the main instance and create a new one, similar to how we do it in web browsers. This feature would be very useful for users who want to compare two terminals side by side.

Currently, it is only possible to reorder tabs within the same Windows Terminal instance. By implementing a new right-click context menu option, such as 'Move tab to new window', users would have the ability to easily create new instances and compare multiple terminals at the same time.

Proposed technical implementation details (optional)

@sur1v sur1v added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Apr 23, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot 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 Apr 23, 2023
@zadjii-msft
Copy link
Member

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

/dup #1256

It's also done, and shipping in 1.18, which is coming out once we sort out the last blocking issues (in #14957)

@microsoft-github-policy-service
Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot 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 Apr 23, 2023
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

2 participants