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

Decide which terminals run in admin mode #6336

Closed
mwpowellhtx opened this issue Jun 3, 2020 · 2 comments
Closed

Decide which terminals run in admin mode #6336

mwpowellhtx opened this issue Jun 3, 2020 · 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

@mwpowellhtx
Copy link

Would be grand if we could determine which terminal tabs ran in elevated admin mode. Or is it that the whole WT process itself is the admin elevation? At least to clarify that part would be acceptable.
Might also be awesome to allow for command line configuration, i.e. run a Visual Studio command prompt from within Windows Terminal, i.e. replete with CLI configuration, parameters, etc, i.e. running the VS variables scripts and so forth. Thanks!
@mwpowellhtx mwpowellhtx added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 3, 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 Jun 3, 2020
@DHowett
Copy link
Member

DHowett commented Jun 3, 2020

/dup #5000 😄

@ghost
Copy link

ghost commented Jun 3, 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 Jun 3, 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 Jun 3, 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
2 participants
@DHowett @mwpowellhtx