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

Update color scheme for any tab/pane on the fly #6141

Closed
hectormz opened this issue May 22, 2020 · 5 comments
Closed

Update color scheme for any tab/pane on the fly #6141

hectormz opened this issue May 22, 2020 · 5 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@hectormz
Copy link

Description of the new feature/enhancement

I'd like to be able to set the color scheme for any tab or pane I have open in Windows Terminal with a command. If I'm temporarily opening multiple instances of the same profile, I'd like to distinguish them by setting the color scheme for that instance to any of the available color schemes I have. The alternative to this would be to go into settings and duplicate profiles, but with different color schemes etc.

I don't believe this has been raised here so far. If it's possible, I have not found it in any documentation yet.

Proposed technical implementation details (optional)

I think this is not yet possible because I don't think are Windows Terminal commands from within Windows Terminal yet. I know you can run wt.exe with some options to configure how a new instance of Windows Terminal is launched.

Assuming there will be a single executable for commands in the future from within Windows Terminal, something like:

<executable.exe> --color "Campbell"

would be nice.

Or even:

wt-color "Campbell"
@hectormz hectormz added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label May 22, 2020
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels May 22, 2020
@zadjii-msft
Copy link
Member

zadjii-msft commented May 22, 2020

So, colortool can't quite yet read color schemes that you have installed in the terminal settings, but I think you can usually find a colortool compatible version of most colorshemes for the Terminal.

Then the workflow with colortool is just colortool -x Campbell.

Then there's also #4472 for "run commands in the current window", and #5401 for "add a shortcut action to switch to a specific color scheme", which will then pair well with #2046/#5400 for "I want to be able to run an action in the current window" (from the command palette). All those together will combine to let you do something like Ctrl+shift+P, "Change colorscheme", (pick the colorscheme), similar to how vscode works.

Does any of that sound like what you're looking for?

@zadjii-msft zadjii-msft added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 22, 2020
@hectormz
Copy link
Author

@zadjii-msft thanks for all the details and links!
I think colortool would help me to start.

#4472/#5401 is more ideal, and picking colorscheme from a command palette would be most ideal.

I have some custom schemes in Terminal settings that would be nice to use instead of figuring out how to hook them up with colortool.

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels May 22, 2020
@amapianosa
Copy link

lets see how it goes

@j4james
Copy link
Collaborator

j4james commented May 24, 2020

The idea of having the colortool read schemes from the Terminal settings was suggested once before in issue #3687 (comment).

@zadjii-msft
Copy link
Member

Okay, since the above solutions sound good, I'll close this in favor of the linked threads. Thanks!

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. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

4 participants