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

Allow to reposition tabs #6927

Closed
anubhms opened this issue Jul 15, 2020 · 5 comments
Closed

Allow to reposition tabs #6927

anubhms opened this issue Jul 15, 2020 · 5 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

@anubhms
Copy link

anubhms commented Jul 15, 2020

Currently the position of tabs in the Terminal are fixed, and when working with large number of tabs it's natural to try and position them together for easier access. And the current fixed tabs layout prevents that, so can we allow to reposition the tabs like you can do in a browser?
@anubhms anubhms added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 15, 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 Jul 15, 2020
@leejy12
Copy link
Contributor

leejy12 commented Jul 15, 2020

Are you running the terminal in administrator mode?

@anubhms
Copy link
Author

anubhms commented Jul 15, 2020

Yes, I am running it in administrator mode.
Just now checked and it allows to re-position tabs in non-elevated mode. Any reasons for that?

@leejy12
Copy link
Contributor

leejy12 commented Jul 15, 2020

Seems like it's due to platform limitation. See #6893

@zadjii-msft
Copy link
Member

Yep, @leejy12's right here.

/dup #6893 #4874 #5564

@ghost
Copy link

ghost commented Jul 15, 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 Jul 15, 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 Jul 15, 2020
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
3 participants
@zadjii-msft @anubhms @leejy12