Hi! On Saturday Jan 25 2014, [email protected] wrote:
> nocolor option is removed though. It still checks for the nocolor env. > variable, if that's what you mean. And the nocolor variable is kept in > mu_config because it's simpler to check against a boolean when printing a > value than an enum. > > I was under the impression that returning false from config_options_set_color > would cause an error (not that I've tried). Anyway, I'll make the changes and > update my pull request Well, the idea would be that if you give, --color=foobar you should get an error. And I think without the 'nocolor' variable would be a bit cleaner, since otherwise we some of the same information stored in two variables. Cheers, Dirk. -- Dirk-Jan C. Binnema Helsinki, Finland e:[email protected] w:www.djcbsoftware.nl pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C -- You received this message because you are subscribed to the Google Groups "mu-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
