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

colortool.exe does not exit after executing #284

New Issue
Open
opened 2026-01-30 21:47:57 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 21:47:57 +00:00
Owner
Copy Link

Originally created by @boompig on GitHub (May 29, 2018).

This bug-tracker is monitored by Windows Console development team and other technical types. We like detail!

If you have a feature request, please post to the UserVoice.

Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.

Please use this form and describe your issue, concisely but precisely, with as much detail as possible

  • Your Windows build number: (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.17134.48]

  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

I'm trying to use the color tool to change the color scheme. Whenever I execute it within cmd.exe, it does not exit. Also the effects (even with --both) don't seem to persist when I close the hung window and open a new one.

  • What's wrong / what should be happening instead:
  1. Color tool does not exit and freezes cmd

To repro:

cd Downloads
colortool.exe --both OneHalfDark

Please see attached screenshot:

screen shot 2018-05-29 at 2 02 53 pm

Originally created by @boompig on GitHub (May 29, 2018). This bug-tracker is monitored by Windows Console development team and other technical types. **We like detail!** If you have a feature request, please post to [the UserVoice](https://wpdev.uservoice.com/forums/266908). > **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible * Your Windows build number: (Type `ver` at a Windows Command Prompt) Microsoft Windows [Version 10.0.17134.48] * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) I'm trying to use the color tool to change the color scheme. Whenever I execute it within cmd.exe, it does not exit. Also the effects (even with `--both`) don't seem to persist when I close the hung window and open a new one. * What's wrong / what should be happening instead: 1. Color tool does not exit and freezes cmd To repro: ``` cd Downloads colortool.exe --both OneHalfDark ``` Please see attached screenshot: ![screen shot 2018-05-29 at 2 02 53 pm](https://user-images.githubusercontent.com/2791268/40685436-1f702bc2-6349-11e8-8307-44258566e899.png)
claunia added the Product-ColortoolHelp WantedIssue-BugArea-Interaction labels 2026-01-30 21:47:57 +00:00
claunia commented 2026-01-30 21:47:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 29, 2018):

Can you right click on the title bar of the "hung" window and click on the "Properties" option? What does the "Colors" Tab look like?

I'd guess that conhost isn't actually hung, it's just rendering white-on-white text for some reason. It might be possible that we're not restoring the fg/bg colors at the end of printing the table.

Does adding the --quiet argument fix it?

@zadjii-msft commented on GitHub (May 29, 2018): Can you right click on the title bar of the "hung" window and click on the "Properties" option? What does the "Colors" Tab look like? I'd guess that conhost isn't actually hung, it's just rendering white-on-white text for some reason. It might be possible that we're not restoring the fg/bg colors at the end of printing the table. Does adding the `--quiet` argument fix it?
claunia commented 2026-01-30 21:47:58 +00:00
Author
Owner
Copy Link

@boompig commented on GitHub (May 29, 2018):

It does look like it's correctly setting everything in the properties window:

screen shot 2018-05-29 at 3 48 04 pm

It also does correctly exit and change the current appearance when --quiet is specified. I suspect you're right about the white text.

However the changes do not persist when I open a new window (--both --quiet)

@boompig commented on GitHub (May 29, 2018): It does look like it's correctly setting everything in the properties window: ![screen shot 2018-05-29 at 3 48 04 pm](https://user-images.githubusercontent.com/2791268/40689601-b8e67f46-6357-11e8-8565-072c36d678e1.png) It also does correctly exit and change the current appearance when `--quiet` is specified. I suspect you're right about the white text. However the changes do not persist when I open a new window (`--both --quiet`)
claunia commented 2026-01-30 21:47:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 29, 2018):

How are you launching cmd?

  • Via the run box (eg. win+r, "cmd")
  • Via the start menu
  • Via the "Start Menu Shortcut" (the one that's brought up when you right click on the start button, also "Win+X, C"
  • Another shortcut
  • some other way?

This actually makes a great deal of difference to how the settings are stored (unfortunately). Most likely, you'll have to actually hit OK in the prop sheet for the changes to persist.

I'd try changing your Text Foreground to something other than white to check if that's it.

@zadjii-msft commented on GitHub (May 29, 2018): How are you launching cmd? * Via the run box (eg. win+r, "cmd") * Via the start menu * Via the "Start Menu Shortcut" (the one that's brought up when you right click on the start button, also "Win+X, C" * Another shortcut * some other way? This actually makes a great deal of difference to how the settings are stored (unfortunately). Most likely, you'll have to actually hit OK in the prop sheet for the changes to persist. I'd try changing your Text Foreground to something other than white to check if that's it.
claunia commented 2026-01-30 21:47:58 +00:00
Author
Owner
Copy Link

@boompig commented on GitHub (May 30, 2018):

  • When launched via ctrl+r cmd: the color scheme is applied, but the colors are not right. For example, here is what OneHalfDark looks like:

screen shot 2018-05-29 at 3 59 27 pm

However you can see that --quiet is not required in this case. I get these results both with and without --quiet.

Same result with launching via start menu.

The initial problem manifested itself via taskbar shortcut right click:

screen shot 2018-05-29 at 4 01 22 pm

And here I am not seeing any theming applied at all

@boompig commented on GitHub (May 30, 2018): - When launched via ctrl+r `cmd`: the color scheme is applied, but the colors are not right. For example, here is what OneHalfDark looks like: ![screen shot 2018-05-29 at 3 59 27 pm](https://user-images.githubusercontent.com/2791268/40689910-4b4fb392-6359-11e8-95b1-6b5427acbe6e.png) However you can see that `--quiet` is not required in this case. I get these results both with and without `--quiet`. Same result with launching via start menu. The initial problem manifested itself via taskbar shortcut right click: ![screen shot 2018-05-29 at 4 01 22 pm](https://user-images.githubusercontent.com/2791268/40689974-8f7a900a-6359-11e8-8e88-de8d968434dc.png) And here I am not seeing any theming applied at all
claunia commented 2026-01-30 21:47:58 +00:00
Author
Owner
Copy Link

@boompig commented on GitHub (May 30, 2018):

When launched via ctrl+r + cmd, I get the view in the previous screenshot. When launched via right click on taskbar, I see this (completely unstyled):

screen shot 2018-05-29 at 4 02 01 pm

@boompig commented on GitHub (May 30, 2018): When launched via ctrl+r + cmd, I get the view in the previous screenshot. When launched via right click on taskbar, I see this (completely unstyled): ![screen shot 2018-05-29 at 4 02 01 pm](https://user-images.githubusercontent.com/2791268/40689987-a4705d00-6359-11e8-987d-823ce9eee750.png)
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-Interaction Help Wanted Issue-Bug Product-Colortool
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#284
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?