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

ColorTool does not resolve schemes properly, and does not work with WSL paths #7373

New Issue
Closed
opened 2026-01-31 01:02:13 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 01:02:13 +00:00
Owner
Copy Link

Originally created by @johnazariah on GitHub (Apr 12, 2020).

Environment

10.0.18363.0

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Ubuntu on WSL

Steps to reproduce

  • on Windows Command Shell/PowerShell/GitBash
    • running ColorTool.exe <schemename> (without extension) does not resolve the scheme
    • running ColorTool.exe <schemename.extension> resolves the scheme correctly.

This behaviour is contrary to the advertised behaviour, which says that the scheme will be resolved trying a specific order of extensions

  • on Ubuntu bash running in WSL
    • running ColorTool.exe -x <schemename> (without extension) does not resolve the scheme
    • running ColorTool.exe -x <schemename.extension> does not resolve the scheme and throws exceptions.

This behaviour is also not the expected behaviour.

Expected behavior

ColorTool.exe OneHalfDark should have the same behaviour as ColorTool.exe OneHalfDark.itermcolors, and should actually load the terminal colors on both Windows shells and WSL shells

Actual behavior

before
before-wsl

Originally created by @johnazariah on GitHub (Apr 12, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **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. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment 10.0.18363.0 ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Terminal version (if applicable): Any other software? ``` Ubuntu on WSL # Steps to reproduce - on Windows Command Shell/PowerShell/GitBash * running `ColorTool.exe <schemename>` (without extension) does not resolve the scheme * running `ColorTool.exe <schemename.extension>` resolves the scheme correctly. This behaviour is contrary to the advertised behaviour, which says that the scheme will be resolved trying a specific order of extensions - on Ubuntu bash running in WSL * running `ColorTool.exe -x <schemename>` (without extension) does not resolve the scheme * running `ColorTool.exe -x <schemename.extension>` does not resolve the scheme and throws exceptions. This behaviour is also not the expected behaviour. <!-- A description of how to trigger this bug. --> # Expected behavior `ColorTool.exe OneHalfDark` should have the same behaviour as `ColorTool.exe OneHalfDark.itermcolors`, and should actually load the terminal colors on both Windows shells and WSL shells <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior <!-- What's actually happening? --> ![before](https://user-images.githubusercontent.com/830311/79059824-3b66f180-7c33-11ea-80f0-fb1686eb0876.JPG) ![before-wsl](https://user-images.githubusercontent.com/830311/79059826-402ba580-7c33-11ea-8f1a-87a3cbe8e8fb.JPG)
claunia commented 2026-01-31 01:02:14 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 12, 2020):

It looks like this might be because your color schemes are in the WSL-only part of the filesystem. We haven’t yet done the compatibility work required to make sure ColorTool can use the new \\wsl$ redirector paths from Windows 19H1.

@DHowett-MSFT commented on GitHub (Apr 12, 2020): It looks like this might be because your color schemes are in the WSL-only part of the filesystem. We haven’t yet done the compatibility work required to make sure ColorTool can use the new `\\wsl$` redirector paths from Windows 19H1.
claunia commented 2026-01-31 01:02:15 +00:00
Author
Owner
Copy Link

@johnazariah commented on GitHub (Apr 12, 2020):

Thanks, @DHowett-MSFT

I've put it a fix that works in my test cases...

https://github.com/microsoft/terminal/pull/5327
after
after-wsl

Hope this helps :)

@johnazariah commented on GitHub (Apr 12, 2020): Thanks, @DHowett-MSFT I've put it a fix that works in my test cases... https://github.com/microsoft/terminal/pull/5327 ![after](https://user-images.githubusercontent.com/830311/79060162-859da200-7c36-11ea-9ed2-02b47459b88d.JPG) ![after-wsl](https://user-images.githubusercontent.com/830311/79060166-87fffc00-7c36-11ea-9b2b-3993bca992f6.JPG) Hope this helps :)
claunia commented 2026-01-31 01:02:15 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 17, 2020):

Thanks for submitting a fix! We're a little behind on pull request reviews right now, but I'll tag this bug up properly in the meantime.

@DHowett-MSFT commented on GitHub (Apr 17, 2020): Thanks for submitting a fix! We're a little behind on pull request reviews right now, but I'll tag this bug up properly in the meantime.
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-CodeHealth Help Wanted Issue-Bug Priority-3 Product-Colortool Resolution-Fix-Committed
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#7373
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?