starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Megathread: sudo, runas, mixed elevation of tabs, etc. #1379

New Issue
Open
opened 2026-01-30 22:24:09 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 22:24:09 +00:00
Owner
Copy Link

Originally created by @hansmbakker on GitHub (May 27, 2019).

Summary of the new feature/enhancement

Current situation:

  • Suppose you are working on something in Powershell, CMD
  • You went into some folder
  • You built some history
  • You find out that you need administrator rights for some command

Currently most console apps (Powershell, CMD) need to start a new session for getting administrator access. This results in a less optimal workflow, because then you lose

  • your current working folder (you need to cd into it again)
  • your command history (the administrator session has its own history)

Proposed technical implementation details (optional)

A bit like sudo, started with a button:

  • Console sessions in terminal start with default permissions
  • Terminal has button with padlock icon / text "upgrade to administrator" in one of the corners
  • When you click the button, the current session is upgraded to a session with admin permissions or downgraded again to normal permissions
  • Session command history and location (working directory) is kept
Originally created by @hansmbakker on GitHub (May 27, 2019). # Summary of the new feature/enhancement Current situation: - Suppose you are working on something in Powershell, CMD - You went into some folder - You built some history - You find out that you need administrator rights for some command Currently most console apps (Powershell, CMD) need to start a new session for getting administrator access. This results in a less optimal workflow, because then you lose - your current working folder (you need to `cd` into it again) - your command history (the administrator session has its own history) # Proposed technical implementation details (optional) A bit like `sudo`, started with a button: - Console sessions in terminal start with default permissions - Terminal has button with padlock icon / text "upgrade to administrator" in one of the corners - When you click the button, the current session is upgraded to a session with admin permissions or downgraded again to normal permissions - Session command history and location (working directory) is kept
claunia added the Issue-FeatureResolution-AnsweredArea-ServerProduct-Meta labels 2026-01-30 22:24:10 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Server Issue-Feature Product-Meta Resolution-Answered
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1379
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?