-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Light Yellow instead of Yellow for Warning Color in Windows #979
Comments
I'll test how the different colours would look later, but
You are not the first one to ask this, see #590. Looking through that and performing a cursory google search says that some debug consoles (in IDEs and stuff) can run into trouble with escape codes. I actually disabled that check for Catch 2 and it is likely to stay disabled (users with trouble can run catch with |
I see. Fingers crossed for BrightYellow ;-) |
Now that version 2 is out, I had hoped for BrightYellow. It is actually quite simple:
Would you please consider adding BrightYellow, as the normal Yellow in Windows Console is muddy and dim... |
Awesome, thank you! Catch continues to be my favorite Unittest framework :-) |
Thanks, and sorry for the long wait. The issue kinda slipped my mind and the backlog is still huge. |
Could you please also add BrightYellow to Catch1? I cannot reopen this issue. Do I need to make a new issue for this request? |
This is only a tiny issue. The non-light colors in Win32 Console are all very dim and boring. Hence, you already use the bright green and bright red. I wonder if you could also use bright yellow for warnings. You use Colour::Yellow for warnings and reconstructed expressions. I have no opinion about whether reconstructed expressions should be yellow or bright yellow.
Since I would like to use bright yellow in my reporter, I would already be happy if you added Colour::BrightYellow.
Also, it took me a while to understand that there are no colors when a debugger is active. I found --use-color, but I don't understand why color and the debugger could harm each other. Could you please explain this briefly?
The text was updated successfully, but these errors were encountered: