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

Set CLICOLORS environment variable #77

Closed
jhasse opened this Issue Apr 28, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@jhasse
Copy link

jhasse commented Apr 28, 2015

Hi!

First of all thanks for ANSICON, I really love it! Makes outputting colored text cross-platform a lot easier.

When I was configuring a Jenkins continuous integration server on Windows I noticed how hard it is to tell all programs that it's okay to output ANSI color codes. There are some programs looking for ANSICON (which of course only works out-of-the-box on cmd.exe, not with Jenkins) and others look for the TERM variable. I think it would be great if there was a standard environment variable for all platforms.

I searched a bit and found that CLICOLOR comes close, but is currently only used on OSX AFAIK. That's why I created a page to document this: http://bixense.com/clicolors/

Would you be willing to set CLICOLOR additionally to ANSICON? If yes, that would be a great first step. I'm also planning to create issues for MSYS 2, Cygwin and various Linux distributions to set this variable.

Thanks in advance and I'm looking forward to your comments on this :)

edit: Miss-spelled CLICOLOR in the title, sorry!

@adoxa

This comment has been minimized.

Copy link
Owner

adoxa commented Apr 29, 2015

I shall add it as a dynamic variable (like ANSICON_VER):

C:\>set cli
Environment variable cli not defined

C:\>echo %CLICOLOR%
1
@jhasse

This comment has been minimized.

Copy link

jhasse commented May 5, 2015

Yes, that would be great :)

@adoxa

This comment has been minimized.

Copy link
Owner

adoxa commented Dec 24, 2017

Done.

@jhasse

This comment has been minimized.

Copy link

jhasse commented Jan 2, 2018

Thanks!

@jhasse jhasse closed this Jan 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment