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

Taskbar Peek (or Terminals title), show if Terminals is elevated. #17649

New Issue
Closed
opened 2026-01-31 05:48:52 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 05:48:52 +00:00
Owner
Copy Link

Originally created by @jefflord on GitHub (Jun 7, 2022).

Description of the new feature/enhancement

It would be great if the Windows Peek feature could be able to let us know if Terminals is elevated. I usually have an elevated and non-elevated terminal and you cannot tell which is which from the Peek:

image

Proposed technical implementation details (optional)

I understand this is likely a "Windows" or "Taskbar" thing to do graphically, so options might be limited. Perhaps as a start, add a new option/setting under Appearance which could be something like "Prefix application title with '🛡' if Terminals is elevated."

I know that cmd and powershell might also "be involved..." since you could do this:

$host.ui.RawUI.WindowTitle = "🛡 : My title"

Also, cmd already prefixes the title with "Administrator"... Since all the things that Terminals might host have different rules, and so do Taskbar... the suggested option might be a good "global" option?

Thanks,
Jeff

Originally created by @jefflord on GitHub (Jun 7, 2022). # Description of the new feature/enhancement It would be great if the Windows Peek feature could be able to let us know if Terminals is elevated. I usually have an elevated and non-elevated terminal and you cannot tell which is which from the Peek: ![image](https://user-images.githubusercontent.com/4396667/172421763-e2b191b0-9544-4869-922a-7502fdf9bc02.png) # Proposed technical implementation details (optional) I understand this is likely a "Windows" or "Taskbar" thing to do graphically, so options might be limited. Perhaps as a start, add a new option/setting under Appearance which could be something like "Prefix application title with '🛡' if Terminals is elevated." I know that cmd and powershell might also "be involved..." since you _could_ do this: $host.ui.RawUI.WindowTitle = "🛡 : My title" Also, cmd already prefixes the title with "Administrator"... Since all the things that Terminals might host have different rules, and so do Taskbar... the suggested option might be a good "global" option? Thanks, Jeff
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 05:48:52 +00:00
claunia commented 2026-01-31 05:48:53 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Jun 7, 2022):

Another graphical idea is to color the terminal tab switch area differently for elevated process. This could allow to quicker visually perceive the difference

@vadimkantorov commented on GitHub (Jun 7, 2022): Another graphical idea is to color the terminal tab switch area differently for elevated process. This could allow to quicker visually perceive the difference
claunia commented 2026-01-31 05:48:53 +00:00
Author
Owner
Copy Link

@jefflord commented on GitHub (Jun 8, 2022):

Another graphical idea is to color the terminal tab switch area differently for elevated process. This could allow to quicker visually perceive the difference

Actually, this is not a thing because all of the tabs are elevated or not. If Terminals could have elevated and non-elevated tabs (which would be great), then what you suggest would be perfect.

Until then, we need to run two instances of Terminals. And when Terminals window is visible you can tell it's elevated by the shield icon in the title:
image

You cannot tell which is elevated by just looking at the Taskbar Peek area:
image

@jefflord commented on GitHub (Jun 8, 2022): > Another graphical idea is to color the terminal tab switch area differently for elevated process. This could allow to quicker visually perceive the difference Actually, this is not a thing because all of the tabs are elevated or not. If Terminals could have elevated and non-elevated tabs (which would be great), then what you suggest would be perfect. Until then, we need to run two instances of Terminals. And when Terminals window is visible you can tell it's elevated by the shield icon in the title: ![image](https://user-images.githubusercontent.com/4396667/172631646-66ce0cb7-0294-4942-9a5e-a79edba7f26a.png) You cannot tell which is elevated by just looking at the Taskbar Peek area: ![image](https://user-images.githubusercontent.com/4396667/172632020-b731c9ab-c6b8-4c92-9dfa-a0a278fac63e.png)
claunia commented 2026-01-31 05:48:53 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 8, 2022):

To try and de-dupe some conversation here:

  • We're tracking "use some variables to format the tab title" in #1320. I could imagine something like titleFormat: "{elevatedShield} {title}" to say "I want the shield emoji in the title when running elevated". That seems like the most flexible way to do something like this.
  • We're tracking "different schemes / themes" in #8311. That should cover both styling the titlebar different, and the individual tabs as well.
  • There's also #3637 for switching which profiles are visible when elevated or not. That feels more hacky. That would be more like "I have a cmd profile that's got a black BG, and an elevated CMD profile that's got a red BG. Only one is visible at a time". That honestly just feels clunky.

I think overall it looks like what you're looking for is best served by #1320, so I'm gonna close this one as a dupe of that. Thanks!

/dup #1320

@zadjii-msft commented on GitHub (Jun 8, 2022): To try and de-dupe some conversation here: * We're tracking "use some variables to format the tab title" in #1320. I could imagine something like `titleFormat: "{elevatedShield} {title}"` to say "I want the shield emoji in the title when running elevated". That seems like the most flexible way to do something like this. * We're tracking "different schemes / themes" in #8311. That should cover both styling the titlebar different, and the individual tabs as well. * There's also #3637 for switching which profiles are visible when elevated or not. That feels more hacky. That would be more like "I have a cmd profile that's got a black BG, and an elevated CMD profile that's got a red BG. Only one is visible at a time". That honestly just feels clunky. I think overall it looks like what you're looking for is best served by #1320, so I'm gonna close this one as a dupe of that. Thanks! /dup #1320
claunia commented 2026-01-31 05:48:54 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 8, 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 commented on GitHub (Jun 8, 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!
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 Issue-Feature Resolution-Duplicate
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#17649
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?