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

Expose ‘true colour’ support in $COLORTERM #2478

Merged
merged 1 commit into from
Nov 22, 2017
Merged

Expose ‘true colour’ support in $COLORTERM #2478

merged 1 commit into from
Nov 22, 2017

Conversation

ELLIOTTCABLE
Copy link

Further discussion here: https://gist.github.com/XVilka/8346728#detection

This environment variable seems to be becoming standardized-upon. That said, although a single-line change, it is increasing the bloat dumped onto the environment by 25%, so feel free to discuss/wait/reject!

<3

@rauchg
Copy link
Member

rauchg commented Nov 21, 2017

+1 from me. Thanks @ELLIOTTCABLE, good to see you here!

@chabou
Copy link
Collaborator

chabou commented Nov 22, 2017

Thank you so much for your help 🙏

@chabou chabou merged commit 57166a5 into vercel:master Nov 22, 2017
chabou added a commit that referenced this pull request Nov 22, 2017
@chabou
Copy link
Collaborator

chabou commented Nov 22, 2017

I reverted my merge, because It should have been merged in canary branch 😞

I will duplicate this PR and target canary

@ELLIOTTCABLE
Copy link
Author

My bad! I didn't even realize there was a separate branch. 🤣

Here's hoping I can contribute more awesome stuff! <3

@Tyriar
Copy link
Contributor

Tyriar commented Nov 28, 2017

@chabou the canary branch doesn't support truecolor though? xtermjs/xterm.js#484

@chabou
Copy link
Collaborator

chabou commented Nov 29, 2017

@Tyriar I totally forgot that. Thank you for your insight

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants