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

Add admin and non-admin Terminal Tabs #12956

Closed
jonasprechtl opened this issue Apr 21, 2022 · 2 comments
Closed

Add admin and non-admin Terminal Tabs #12956

jonasprechtl opened this issue Apr 21, 2022 · 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

@jonasprechtl
Copy link

Description of the new feature/enhancement

When working with the Terminal, I usually work with no admin privileges because I would have to take the extra step to right-click and run as administrator. Sometimes, however, I need an admin terminal for a Task. It would be nice if it was possible to mix admin and non Admin Terminal Tabs in one window, so when I have to run as administrator, I wouldn't have to work with two terminal instances at once and remember which instance is which.
I suggest a setting to enable this feature for individual Consoles (e.g. only PowerShell or PowerShell and cmd, ...).
The User should be able to add normal and Admin Terminal Tabs to the Window by just clicking on the Add Tab Symbol and selecting Admin or non-Admin consoles.
The Terminal Tabs with admin Privileges should be clearly marked as Admin, maybe with a red color or a Symbol to make it easier for the User to navigate and tell them Apart.

Proposed technical implementation details (optional)

@jonasprechtl jonasprechtl added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Apr 21, 2022
@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 Apr 21, 2022
@zadjii-msft
Copy link
Member

Alas, as much as we'd like to do this, it's simply not going to be possible.

See this doc for a bit more of the reasoning, as well as Elevation Quality of Life Improvements.

In 1.13, you can ctrl+click on a profile to launch it in a new elevated window automatically:
image

That's not really the same as putting the same window, but it's a little more convenient. /dup #1032

@ghost
Copy link

ghost commented Apr 21, 2022

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 Apr 21, 2022
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