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

Allow color fields to refer back to the active color scheme (like "cursorColor = yellow") #10479

New Issue
Open
opened 2026-01-31 02:22:43 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 02:22:43 +00:00
Owner
Copy Link

Originally created by @vefatica on GitHub (Sep 3, 2020).

I can't do this

"cursorColor": "yellow"

AFAICT, to get a "yellow" cursor I must (look up and) hard code the "yellow" value from the current theme.

Is there a better way? If not I suggest that you allow color names for "cursorColor"

And what's the difference between "#rgb" and "#rrggbb"?

Originally created by @vefatica on GitHub (Sep 3, 2020). I can't do this "cursorColor": "yellow" AFAICT, to get a "yellow" cursor I must (look up and) hard code the "yellow" value from the current theme. Is there a better way? If not I suggest that you allow color names for "cursorColor" And what's the difference between "#rgb" and "#rrggbb"?
claunia added the Area-SettingsIssue-TaskProduct-Terminal labels 2026-01-31 02:22:44 +00:00
claunia commented 2026-01-31 02:22:44 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 3, 2020):

I was sure that we had a feature request for this already, but it looks like we don't! Thanks!

The difference between #rgb and #rrggbb is that #rgb is shorter.

@DHowett commented on GitHub (Sep 3, 2020): I was sure that we had a feature request for this already, but it looks like we don't! Thanks! The difference between `#rgb` and `#rrggbb` is that `#rgb` is shorter.
claunia commented 2026-01-31 02:22:45 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 3, 2020):

Link: #3327

@DHowett commented on GitHub (Sep 3, 2020): Link: #3327
claunia commented 2026-01-31 02:22:45 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 3, 2020):

Link: #5776

@DHowett commented on GitHub (Sep 3, 2020): Link: #5776
claunia commented 2026-01-31 02:22:45 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Sep 3, 2020):

I searched too (but not as hard as you).

And/or ... allow an integer index in the palette, as in

"cursorColor": 3 // "yellow"

@vefatica commented on GitHub (Sep 3, 2020): I searched too (but not as hard as you). And/or ... allow an integer index in the palette, as in "cursorColor": 3 // "yellow"
claunia commented 2026-01-31 02:22:45 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Sep 3, 2020):

The difference between #rgb and #rrggbb is that #rgb is shorter.

That's obvious. :-) Is there any difference in their use? Is there any alternative to "#123456"?

@vefatica commented on GitHub (Sep 3, 2020): _The difference between #rgb and #rrggbb is that #rgb is shorter._ That's obvious. :-) Is there any difference in their use? Is there any alternative to "#123456"?
claunia commented 2026-01-31 02:22:46 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 3, 2020):

Nah. I believe the #rgb shorthand comes from CSS, and as such is very convenient for web color grading. You specify one nybble for each color, and that nybble is copied over the one you didn't specify: #c12 becomes #cc1122 and #fff becomes #ffffff.

There's no shorthand for #123456 (nor can there ever be?) because there's no way to specify the same amount of information by specifying less information 😉

@DHowett commented on GitHub (Sep 3, 2020): Nah. I believe the `#rgb` shorthand comes from CSS, and as such is very convenient for _web color grading_. You specify one nybble for each color, and that nybble is copied over the one you didn't specify: `#c12` becomes `#cc1122` and `#fff` becomes `#ffffff`. There's no shorthand for `#123456` (nor can there ever be?) because there's no way to specify the same amount of information _by specifying less information_ 😉
claunia commented 2026-01-31 02:22:46 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Sep 3, 2020):

You specify one nybble for each color, and that nybble is copied over the one you didn't specify: #c12 becomes #cc1122 and #fff becomes #ffffff.

Thanks for the explanation. That's odd. I never saw it before.

@vefatica commented on GitHub (Sep 3, 2020): _You specify one nybble for each color, and that nybble is copied over the one you didn't specify: #c12 becomes #cc1122 and #fff becomes #ffffff._ Thanks for the explanation. That's odd. I never saw it before.
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-Task 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#10479
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?