Hi Christian,
I'm a bit surprised as the --no-color is always possible and you can
also create an alias.
So, if the issue is color or not color, I would recommend just a
--no-color alias.
If the colors themselves, then, no problem to use term colors and so
create a Jira.
Regards
JB
On 11/21/2016 10:15 AM, Christian Schneider wrote:
I fully agree with Brad that the default color is not very readable. It
also makes it difficult for users to change their terminal colors on
their client.
So I propose we change the default log color to the default terminal
color and only use other colors to highlight special things like
exceptions.
If we agree on this I will open a jira issue (if Brad does not do it
before) and change the color.
Christian
On 07.11.2016 17:34, Brad Johnson wrote:
I realize that Aries isn't the keeper of Karaf but there is more than
a little cross-pollination and I'm not on that mailing list. This is
a small but persistent concern.
It really is time for the default logging colors in Karaf to be
changed. They've been atrocious to read for a very long time. Yes,
they can be changed but I'm bouncing from client to client and version
to version and it's a hassle and reading burgundy on black is tiring
on the eyes and cyan on black isn't much of a step in the right
direction.
I'm sure most developers are like I and live in the log files and
tail:log constantly. Something as simple as a modification of the
color scheme would go a long way toward make the log files easier to
work with.
I'd be willing to say that a color change, any color change, would be
better than the defaults.
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
