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.

Sign up for GitHub

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

Jump to bottom

Detaching panes and tabs #8244

Closed
ivancho-ifa opened this issue Nov 12, 2020 · 3 comments
Closed

Detaching panes and tabs #8244

ivancho-ifa opened this issue Nov 12, 2020 · 3 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

@ivancho-ifa
Copy link

Hello team!

First I want to congratulate you on the great job. The Terminal looks awesome! Here is a suggestion that I think will boost productivity and usability.

It would be nice if there is an option to detach tabs and panes to separate Terminal windows. This will be very useful when working with multiple screens or use consoles a lot.

My vision is to be able to drag and drop a tab out of the Terminal window so that it becomes a separate Terminal window which I could send to another screen or virtual monitor. To detach a pane I think there should be a palette command to send the current pane to a separate tab and then I could drag and drop it to a new window.

What do you think of the idea? Let me know if I could help with something!

Best regards,
Ivan Mollov
@ivancho-ifa ivancho-ifa added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 12, 2020
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Nov 12, 2020
@zadjii-msft
Copy link
Member

Thanks for the request! Please make sure to search for duplicates when filing new issues. This is already being tracked by another issue on our repo - please refer to #1256 for more discussion.

/dup #1256
/dup #7507
/dup #4587

@ghost
Copy link

ghost commented Nov 12, 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 closed this as completed Nov 12, 2020
@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 Nov 12, 2020
@ivancho-ifa
Copy link
Author

Sorry for the duplication!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ivancho-ifa @zadjii-msft