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.

Sign up for GitHub

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

Jump to bottom

Set COLORTERM environment variable to truecolor in linux #13687

Closed
XenoBino opened this issue Aug 5, 2022 · 2 comments
Closed

Set COLORTERM environment variable to truecolor in linux #13687

XenoBino opened this issue Aug 5, 2022 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@XenoBino
Copy link

XenoBino commented Aug 5, 2022

Description of the new feature/enhancement

#2785 Might be relevant

Many programs check if COLORTERM environment variable is set to truecolor to determine whether the terminal supports true colors. And since this terminal supports true colors, it would make sense for COLORTERM to be set to truecolor automatically for linux profiles.

Proposed technical implementation details (optional)

I suppose this would require the feature proposed by #2785.
@XenoBino XenoBino added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Aug 5, 2022
@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 Aug 5, 2022
@zadjii-msft
Copy link
Member

Thanks for the suggestion! Please make sure to search for duplicates when filing new issues. This is already being tracked by another issue on our repo - please refer to #11057 for more discussion.

/dup #11057

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Aug 5, 2022
@ghost
Copy link

ghost commented Aug 5, 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 closed this as completed Aug 5, 2022
@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 Needs-Tag-Fix Doesn't match tag requirements labels Aug 5, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zadjii-msft @XenoBino