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

Terminal and ColorTool #20514

New Issue
Closed
opened 2026-01-31 07:16:14 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 07:16:14 +00:00
Owner
Copy Link

Originally created by @Babscoole on GitHub (Sep 19, 2023).

Windows Terminal version

multiple

Windows build number

multiple

Other Software

No response

Steps to reproduce

We have a batch based console app. Trying to use ColorTool to set a custom scheme for use when our batch runs. When Windows Console host is set as the default console, ColorTool can read and display the colors we've set in the .ini just fine. When default console is set to Terminal, it's ignored and not used.

Expected Behavior

Specified .ini is used for Terminal

Actual Behavior

Specified .ini is not used for Terminal

Originally created by @Babscoole on GitHub (Sep 19, 2023). ### Windows Terminal version multiple ### Windows build number multiple ### Other Software _No response_ ### Steps to reproduce We have a batch based console app. Trying to use ColorTool to set a custom scheme for use when our batch runs. When Windows Console host is set as the default console, ColorTool can read and display the colors we've set in the .ini just fine. When default console is set to Terminal, it's ignored and not used. ### Expected Behavior Specified .ini is used for Terminal ### Actual Behavior Specified .ini is not used for Terminal
claunia added the Issue-QuestionNeeds-TriageResolution-Answered labels 2026-01-31 07:16:15 +00:00
claunia commented 2026-01-31 07:16:16 +00:00
Author
Owner
Copy Link

@Babscoole commented on GitHub (Sep 19, 2023):

This is when default console is set to Windows Console Host. Displays and uses the custom scheme we want:

When default console is set to Console Host

This is when default console is set to Terminal. Does not display and use the custom scheme we want:

When default console is set to Terminal

@Babscoole commented on GitHub (Sep 19, 2023): This is when default console is set to Windows Console Host. Displays and uses the custom scheme we want: ![When default console is set to Console Host](https://github.com/microsoft/terminal/assets/82686995/7adc8169-b356-4a73-9dd2-846160e4799c) This is when default console is set to Terminal. Does not display and use the custom scheme we want: ![When default console is set to Terminal](https://github.com/microsoft/terminal/assets/82686995/db1fc6f3-7fda-4035-9b4f-2db57bceaefa)
claunia commented 2026-01-31 07:16:16 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 19, 2023):

This is due to #2985.

You need to run colortool.exe with either the --xterm or -x parameter. This works on Windows 10 build 17048 and later for both the old console window and the new Windows Terminal.

@lhecker commented on GitHub (Sep 19, 2023): This is due to #2985. You need to run `colortool.exe` with either the `--xterm` or `-x` parameter. This works on Windows 10 build 17048 and later for both the old console window and the new Windows Terminal.
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-Question Needs-Triage Resolution-Answered
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#20514
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?