Colorless, narrower output about padpo

[vpoulailleau]

Bonus: By sticking to gcc error format we could easily use padpo in vim/emacs :]

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.

[JulienPalard]

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 --color flag to opt-in, not a --no-color flag to opt out, but I'm not sure to be able to convince you twice on this one :]]

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 :]]]]

[Seluj78]

I agree with Julien,
I'd prefer to color the text instead of the background. As for what to color, idc

[vpoulailleau]

@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 😛

[Seluj78]

I prefer the opt out for colors even if it isnt standard

[deronnax]

+1 : general background color makes it unreadable. An outpout like grep would perfect (normal, with important parts in red)
Also the sharps as delimiters are not a good idea :).