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

Colors not applied correctly #20

New Issue
Open
opened 2026-01-30 21:39:53 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 21:39:53 +00:00
Owner
Copy Link

Originally created by @bantya on GitHub (Aug 29, 2017).

Starting the cmd with two different ways gives Cmd Prompt in two different color variants.

Image 1:
image

Image 2:
image

I have applied color scheme with colortool -b color-theme-name and also opened Properties sheet and hit Ok as mentioned in the colortool -h. This is supposed to apply the chosen color scheme to both: current and default consoles, but surprisingly I get two different results.

The Image 1 console retains the specified color scheme while the Image 2 console displays the default legacy color scheme.

I get Image 1 color scheme when starting the console using:

  1. Start + R > cmd
  2. Start + X > Command Prompt (Admin)
  3. Shift + Right click > Open command window here in explorer window
  4. Alt + D and typing %comspec% in explorer window

and get the Image 2 color scheme using:

  1. Start menu > cmd, Start + S > cmd and Start + Q > cmd
  2. Start + X > Command Prompt

This is somewhat inconsistent behavior; so please improve it.

This tool is the first awesome tool we Windows CMD lovers got in a while thus we believe that it should be perfect which will eventually make command prompt great again!!

Originally created by @bantya on GitHub (Aug 29, 2017). Starting the cmd with two different ways gives Cmd Prompt in two different color variants. **Image 1:** ![image](https://user-images.githubusercontent.com/16685565/29833948-da063230-8d0a-11e7-822a-dc5050263df1.png) **Image 2:** ![image](https://user-images.githubusercontent.com/16685565/29833970-f12d7a5e-8d0a-11e7-8da2-f68e4a140989.png) I have applied color scheme with `colortool -b color-theme-name` and also opened `Properties` sheet and hit `Ok` as mentioned in the `colortool -h`. This is supposed to apply the chosen color scheme to both: current and default consoles, but surprisingly I get two different results. The Image 1 console retains the specified color scheme while the Image 2 console displays the default legacy color scheme. I get Image 1 color scheme when starting the console using: 1. `Start + R > cmd` 2. `Start + X > Command Prompt (Admin)` 3. `Shift + Right click > Open command window here` in explorer window 4. `Alt + D` and typing `%comspec%` in explorer window and get the Image 2 color scheme using: 1. `Start menu > cmd`, `Start + S > cmd` and `Start + Q > cmd` 2. `Start + X > Command Prompt` This is somewhat inconsistent behavior; so please improve it. This tool is the first awesome tool we Windows CMD lovers got in a while thus we believe that it should be perfect which will eventually **_make command prompt great again!!_**
claunia added the Product-ConhostResolution-By-Design labels 2026-01-30 21:39:54 +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 Product-Conhost Resolution-By-Design
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#20
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?