Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve ColorTool to see different schemes in Terminal #12736

Closed
cinnamon-msft opened this issue Mar 21, 2022 · 3 comments
Closed

Improve ColorTool to see different schemes in Terminal #12736

cinnamon-msft opened this issue Mar 21, 2022 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Colortool This is a problem with the utility application ColorTool for manipulating the console color palette. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@cinnamon-msft
Copy link
Contributor

As a tool for being able to see these schemes applied in a terminal, I wrote this cmd script, ansi-colors.cmd, which can be used to put all the SGR parameters together. It is currently configured for showing 1, 4, 7, 30-37, 40-47, and 100-107, and the combinations of those which make sense.

ansi-color cmd

While not written for creating this specific color scheme, I think this might be a tool worth adding to the repo to make it easier to see the different color combinations. It is all self-contained in one .cmd file with no necessary external dependencies. There is an option to use PowerShell to generate the ESC non-printable character, but in this gist it just uses one saved in the file. There is also an optional dependency on CHCP if the output is going to show Unicode, but it does not need to be required. It uses a data segment embedded in the file itself, so the definition of what is shown can quickly and easily be changed to something else.

Originally posted by @rbeesley in #6176 (comment)

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 21, 2022
@cinnamon-msft cinnamon-msft added Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Colortool This is a problem with the utility application ColorTool for manipulating the console color palette. Area-Theming Anything related to the theming of elements of the window labels Mar 21, 2022
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Mar 21, 2022
@rbeesley
Copy link
Contributor

If you want to keep this open to do more work in ColorTool, be my guest. The script I mentioned in the original comment was turned into issue #6470. And resolved in preview 1.13.10336.0, merging #11932. I also started documenting how it works in more depth in a series on Medium (https://link.medium.com/rfc9rux6Aob).

@zadjii-msft
Copy link
Member

This was a bit of a miscommunication - sorry for the confusion folks!

/dup #6470

@ghost
Copy link

ghost commented Mar 22, 2022

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Mar 22, 2022
@zadjii-msft zadjii-msft removed the Area-Theming Anything related to the theming of elements of the window label Mar 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Colortool This is a problem with the utility application ColorTool for manipulating the console color palette. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants