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

The colors taken from the config are too bright for what they actually are #17306

New Issue
Open
opened 2026-01-31 05:38:29 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 05:38:29 +00:00
Owner
Copy Link

Originally created by @nlguerra2003 on GitHub (Apr 21, 2022).

Windows Terminal version

1.12.10983.0

Windows build number

10.0.22598.0

Other Software

No other programs are used

Steps to reproduce

I have this colour scheme (based on the Brave Contrast VScode theme)

{
 "background": "#050607",
 "black": "#1B1E25",
 "blue": "#63A5A5",
 "brightBlack": "#3B4251",
 "brightBlue": "#8db6c9",
 "brightCyan": "#C3BCFF",
 "brightGreen": "#FF8C41",
 "brightPurple": "#C3BCFF",
 "brightRed": "#FF8C41",
 "brightWhite": "#FFFFFF",
 "brightYellow": "#C3BCFF",
 "cursorColor": "#F8F8F0",
 "cyan": "#908BBC",
 "foreground": "#D6DBDB",
 "green": "#BC4331",
 "name": "My Brave Contrast",
 "purple": "#908BBC",
 "red": "#BA0E2E",
 "selectionBackground": "#FFFFFF",
 "white": "#E4E7E7",
 "yellow": "#908BBC"
}

Working with this Powershell $PROFILE1 file:

function Check-IsElevated
{
  $id = [System.Security.Principal.WindowsIdentity]::GetCurrent()
  $p = New-Object System.Security.Principal.WindowsPrincipal($id)
  if ($p.IsInRole([System.Security.Principal.WindowsBuiltInRole]::Administrator))
    { Write-Output $true }      
  else
    { Write-Output $false }   
}

$curUser= (Get-ChildItem Env:\USERNAME).Value
$curComp= (Get-ChildItem Env:\COMPUTERNAME).Value

function prompt {
	if(Check-IsElevated)
	{Write-Host "┌" -nonewline -foreground red}
	else
	{Write-Host "┌" -nonewline}
	Write-Host " $curUser@$curComp" -nonewline -foreground blue
	Write-Host " $(Get-Location)" -foreground cyan
	if(Check-IsElevated)
	{
		Write-Host "└ PS " -foreground red -nonewline
		return "# "
	}
	return "└ PS $ "
}

Expected Behavior

Since the outputted username and location are coded to be represented in blue and cyan, repectively, once they're printed the colors we see in the terminal should be #63A5A5 and #908BBC (again, respectively), looking at what is configured in the scheme.

Actual Behavior

Instead of using the colors that are configured, (remember, #63A5A5 and #908BBC for blue and cyan respectively), if I use PowerToys' color picker I can see the colors used are #8db6c9 and #C3BCFF, just brighter variants of the coded colors.

I don't think I've configured anything that could change the color representation/perception, but any heads-up is appreciated.

Originally created by @nlguerra2003 on GitHub (Apr 21, 2022). ### Windows Terminal version 1.12.10983.0 ### Windows build number 10.0.22598.0 ### Other Software No other programs are used ### Steps to reproduce I have this colour scheme (based on the Brave Contrast VScode theme) ``` { "background": "#050607", "black": "#1B1E25", "blue": "#63A5A5", "brightBlack": "#3B4251", "brightBlue": "#8db6c9", "brightCyan": "#C3BCFF", "brightGreen": "#FF8C41", "brightPurple": "#C3BCFF", "brightRed": "#FF8C41", "brightWhite": "#FFFFFF", "brightYellow": "#C3BCFF", "cursorColor": "#F8F8F0", "cyan": "#908BBC", "foreground": "#D6DBDB", "green": "#BC4331", "name": "My Brave Contrast", "purple": "#908BBC", "red": "#BA0E2E", "selectionBackground": "#FFFFFF", "white": "#E4E7E7", "yellow": "#908BBC" } ``` Working with this Powershell $PROFILE1 file: ``` function Check-IsElevated { $id = [System.Security.Principal.WindowsIdentity]::GetCurrent() $p = New-Object System.Security.Principal.WindowsPrincipal($id) if ($p.IsInRole([System.Security.Principal.WindowsBuiltInRole]::Administrator)) { Write-Output $true } else { Write-Output $false } } $curUser= (Get-ChildItem Env:\USERNAME).Value $curComp= (Get-ChildItem Env:\COMPUTERNAME).Value function prompt { if(Check-IsElevated) {Write-Host "┌" -nonewline -foreground red} else {Write-Host "┌" -nonewline} Write-Host " $curUser@$curComp" -nonewline -foreground blue Write-Host " $(Get-Location)" -foreground cyan if(Check-IsElevated) { Write-Host "└ PS " -foreground red -nonewline return "# " } return "└ PS $ " } ``` ### Expected Behavior Since the outputted username and location are coded to be represented in blue and cyan, repectively, once they're printed the colors we see in the terminal should be #63A5A5 and #908BBC (again, respectively), looking at what is configured in the scheme. ### Actual Behavior Instead of using the colors that are configured, (remember, #63A5A5 and #908BBC for blue and cyan respectively), if I use PowerToys' color picker I can see the colors used are #8db6c9 and #C3BCFF, just brighter variants of the coded colors. I don't think I've configured anything that could change the color representation/perception, but any heads-up is appreciated.
claunia added the Needs-TriageIssue-BugNeeds-Tag-Fix labels 2026-01-31 05:38:30 +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 Issue-Bug Needs-Tag-Fix Needs-Triage
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#17306
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?