-
Notifications
You must be signed in to change notification settings - Fork 35
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
Some airbrussh output is "invisible" in certain terminal color schemes #84
Comments
Same issue here. I'm using the 'Solarized' Color Scheme of KDE's Konsole in version 15.08.0 as provided by Ubuntu 15.10. |
I'm using 'Solarized' Color Scheme on Ubuntu Gnome 16.04 On Tue, Jul 26, 2016 at 6:47 PM, Simon Hürlimann [email protected]
|
Great, looks like we've got this figured out. I know that solarized is popular, and I don't want Airbrussh to obscure important messages when people are using it with solarized. I think that warrants changing Airbrussh's default colors (even if solarized is ultimately at fault). Do you agree? Right now Airbrussh uses the gray to display |
Cool! I'd go with the default color, like the irb output. |
Any chance you'd be willing to do a PR? It should just be a matter of removing the use of |
Yepp, can give it a try:-) |
When using the `gray` color on some implementation of the `solarized` theme the text is not visible. The `solarized` theme is popular and bugs have been reported about missed error messages, so this patch switches these messages to the default color. Fixes mattbrictson#84
PR created, please review:-) |
@mattbrictson upstream issue filed in KDE: https://bugs.kde.org/show_bug.cgi?id=366143 @dan-klasson maybe you want to also file an issue in Gnome and link this and the KDE bug. |
We've received multiple reports (from @Startouf and @dan-klasson in capistrano/capistrano#1669) that important error messages are not being rendered by Airbrussh.
Specifically, the color of the message is indistinguishable from the background color of the terminal, making them "invisible".
Suggestions of how to reproduce this (what OS and terminal is affected?) and how to fix it would be greatly appreciated.
The text was updated successfully, but these errors were encountered: