-
-
Notifications
You must be signed in to change notification settings - Fork 152
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
honor CLICOLOR and CLICOLOR_FORCE #302
Conversation
resolve #307 |
@lelongg Are you able to resolve the conflicts on this branch? |
it is resolved |
@lelongg excellent work.
|
I submitted points 1 and 2. About the tests I'm not sure how to handle this, I didn't find examples of tests checking the logs output in the code, can you help ? |
No problem, I would create a new example in the examples dir that utilizes (or does not utilize) the feature. |
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #302 +/- ##
==========================================
- Coverage 61.12% 60.81% -0.32%
==========================================
Files 23 23
Lines 1407 1429 +22
==========================================
+ Hits 860 869 +9
- Misses 547 560 +13 ☔ View full report in Codecov by Sentry. |
@lelongg Take a look at my branch #335 which makes the changes for windows. I'm not sure the right way to test this in the CI though (or in windows). I tested the linux version running locally but I don't have a windows env to test in. I didn't take @estk's suggestion on the integration example with std::process yet, instead I took the lazy way out in the CI. |
Interesting, I swapped over to a new test using exe. It works fine locally but weird results in the CI, but |
add support of CLICOLOR to disable color output and CLICOLOR_FORCE to force color output
See https://bixense.com/clicolors/