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

Conditional settings - i.e. different colors when Administrator #4532

New Issue
Open
opened 2026-01-30 23:49:49 +00:00 by claunia · 4 comments
claunia commented 2026-01-30 23:49:49 +00:00
Owner
Copy Link

Originally created by @DavJenkins on GitHub (Oct 18, 2019).

Description of the new feature/enhancement

As a user, it would be nice to be able to specify different color schemes based on some conditions.

For decades (ever since an errant recursive remove command executed as root) I have used light cyan on dark blue for normal command windows and bright white on red when I am operating as root or Administrator just to remind myself to be extra careful.

Proposed technical implementation details (optional)

This notion could be generalized as conditional profiles (or conditional attributes within a profile) to be applied when a specified expression evaluates to true. Conditional profiles (and/or attributes) would be guaranteed to be applied after all unconditional ones so they would override any default specifications, thus eliminating the need to add "else" or inverted duplicate conditionals. Order of evaluation/application of conditionals would be undefined (or, if you really want to get wild, they could be prioritized then undefined ordering among equal priorities).

When invoked as Administrator, any profile or attribute that was tagged as conditional based on having Administrator access would be applied; otherwise not. In my use case, any window I opened as me would be pleasantly colored while any window opened as Administrator would be "remember you're ROOT, stupid!" colored.

Originally created by @DavJenkins on GitHub (Oct 18, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement As a user, it would be nice to be able to specify different color schemes based on some conditions. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> For decades (ever since an errant recursive remove command executed as root) I have used light cyan on dark blue for normal command windows and bright white on red when I am operating as root or Administrator just to remind myself to be extra careful. # Proposed technical implementation details (optional) This notion could be generalized as conditional profiles (or conditional attributes within a profile) to be applied when a specified expression evaluates to true. Conditional profiles (and/or attributes) would be guaranteed to be applied after all unconditional ones so they would override any default specifications, thus eliminating the need to add "else" or inverted duplicate conditionals. Order of evaluation/application of conditionals would be undefined (or, if you really want to get wild, they could be prioritized then undefined ordering among equal priorities). <!-- A clear and concise description of what you want to happen. --> When invoked as Administrator, any profile or attribute that was tagged as conditional based on having Administrator access would be applied; otherwise not. In my use case, any window I opened as me would be pleasantly colored while any window opened as Administrator would be "**remember you're _ROOT_, stupid!**" colored.
claunia added the Issue-FeatureArea-SettingsProduct-Terminal labels 2026-01-30 23:49:49 +00:00
claunia commented 2026-01-30 23:49:50 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 21, 2019):

This is related to #3062.

@DHowett-MSFT commented on GitHub (Oct 21, 2019): This is related to #3062.
claunia commented 2026-01-30 23:49:50 +00:00
Author
Owner
Copy Link

@trajano commented on GitHub (Jan 3, 2023):

In my dup https://github.com/microsoft/terminal/issues/14593 I added a proposal on how it would be implemented.

@trajano commented on GitHub (Jan 3, 2023): In my dup https://github.com/microsoft/terminal/issues/14593 I added a proposal on how it would be implemented.
claunia commented 2026-01-30 23:49:51 +00:00
Author
Owner
Copy Link

@mhechthz commented on GitHub (Aug 9, 2023):

Any new development on this? I also would really appreciate this.

@mhechthz commented on GitHub (Aug 9, 2023): Any new development on this? I also would really appreciate this.
claunia commented 2026-01-30 23:49:51 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 10, 2023):

Nope. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button?
image
That way you'll be notified of any updates to this thread, without needlessly pinging everyone on this thread ☺️

#11111 has also become a bit of a megathread tracking all these topics.

@zadjii-msft commented on GitHub (Aug 10, 2023): Nope. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button? ![image](https://user-images.githubusercontent.com/18356694/91237459-5cbb0c80-e700-11ea-9347-b9b1ec2813b1.png) That way you'll be notified of any updates to this thread, without needlessly pinging everyone on this thread ☺️ #11111 has also become a bit of a megathread tracking all these topics.
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-Settings Issue-Feature Product-Terminal
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#4532
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?