-
Notifications
You must be signed in to change notification settings - Fork 5
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
Colorless, narrower output #15
Comments
You convinced me! 😉 I think that I'll add a CLI flag to enable this, because the color allows to see rapidly the errors (skipping the warnings first). So I prefer to also keep this functionality. |
I'd say do as most CLI programs: a Also while I'm at it, I feel that foreground color is more readable than background color, at least on my color scheme, but I'm not sure to be able to convince you three times on this one :]]] Also while I'm at it, I'd color only the "warning" / "error" string not the whole string, but I'm not sure to be able to convice you 4 times on this one :]]]] |
I agree with Julien, |
@JulienPalard @Seluj78 For the readability issues, I'm using the default colors of http://github.com/vpoulailleau/simplelogging but changing those coloring choices is on my pretty old TODO list 😉 You almost made a strike there, at least a spare! The last point for which I'm not totally convinced yet is opt-in/opt-out for color. But I don't have the time to code right now, we'll see the decision later 😉 But "I'd say do as most CLI programs" is quite a valid argument 😛 |
I prefer the opt out for colors even if it isnt standard |
+1 : general background color makes it unreadable. An outpout like grep would perfect (normal, with important parts in red) |
Logs are hard to read:
I think they should be narrower and maybe with less colors, at least no background color. why not sticking to gcc-style errors, as an example:
Could be more readable as:
Note that in github the wide version is so wide we have literally no relevant information in the screen :(
Bonus: By sticking to gcc error format we could easily use padpo in vim/emacs :]
The text was updated successfully, but these errors were encountered: