Issac Goldstand wrote: > I don't know if my vote counts, but... > -1 to turning off colors. > I was delighted to see them - it made more critical points during the > build/test process much easier to catch as they went by. I'm not saying > that we can't look into improving them somehow (either better > combinations or trying to figure out the bg color [if that's possible], > or making it easier to turn them off - or even turning them off by > default and just making them easier to turn on [I'd never in a million > years find APACHE_TEST_COLOR, nor would I ever think to turn them on on > my own even if I did find the directive])
Issac, I don't want them to be off by default too. The "original" idea came from the gcc-color wrapper, but now I see that it has gone from gcc. Probably it has caused more complaints than it was helpful. If you are willing to write a short test script that simply prints a few colored messages, ask the modperl users on various platforms/terms to run it and figure out a colormap working everywhere. If we find one that would be great! For now we will turn the colors off by default and you can enable them with APACHE_TEST_COLOR env var in your ~/.profile or equiv. Since you will miss the color you will remember to set this env var :) Others new to 2.0 will find this option in the docs. __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
