On Wed, Feb 14, 2018 at 08:26:46AM +0100, Eugen.Wiens@xxxxxxxx wrote: > Hi Sascha, > > Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> schrieb am 13.02.2018 09:37:17: > > > Von: Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> > > An: Eugen Wiens <eugen.wiens@xxxxxxxx> > > Kopie: barebox@xxxxxxxxxxxxxxxxxxx > > Datum: 13.02.2018 09:37 > > Betreff: Re: [PATCH] added colored print out of log levels > > > > HI Eugen, > > > > On Fri, Feb 09, 2018 at 01:28:45PM +0100, Eugen Wiens wrote: > > > When the system is booting the warnings and errors are not be > > quickly discovered. > > > With this improvement the errors are colored red, the warnings > > yellow and the notices blue. > > > > I like this because I like colors ;) > > However, some people do not. Can we make this honour the value of the > > global.allow_color variable? > That sounds good for me. > > > This variable is currently only used in the > > environment, so we would have to move it to C code by adding a > > globalvar_add_simple_bool(). > Where is the best place to call this function, inside the file > "console_common.c" or That would be a suitable place. You could rename loglevel_init to console_common_init for example. > on a more generic place. Which file is the best one to learn the handling > of the > function "globalvar_add_simple_bool"? You pass it an int pointer which is treated as boolean variable. Setting the globalvar on the command line directly changes the integer variable. Other than that, grep the source, there are not so many users of that function. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
