Closed gruber76 closed 10 years ago
+1 That would be fantastic - I'm a poor soul stuck on Windows. It would be a shame to loose all the colors by using --no-color. Thanks @gruber76!
Would this be too ham-fisted? (assuming some documentation additions to grunt.log, as well.)
https://github.com/gruber76/grunt/commit/a56a71d960ac02fc960de1266c2f05441357c84b
@gruber76 You can customize this in your terminal app. For someone with color vision deficiencies, that would be a much better route, as it would affect all of the tools they use in a uniform fashion. We won't be adding this complexity to Grunt, sorry :(
How can I do this then? (using windows)
Oh, I wasn't looking to change the color of the entire command prompt - just the blue errors by Grunt
On Mon, Jul 14, 2014 at 2:01 PM, Sindre Sorhus notifications@github.com wrote:
— Reply to this email directly or view it on GitHub https://github.com/gruntjs/grunt/issues/1128#issuecomment-48891795.
Grunt is just using the standard colors in your prompt. You change it there. Nothing to do with grunt.
In addition to consistency and semantic styling (#957 and #697) I propose that the colors used by grunt.log need to be configurable. --no-color is a passable stop-gap, but for those with color vision deficiency or (in the extreme) using Windows, a configurable output would be even better.
Obviously, if the colors are stored in config but an error happens before (or while) the configs are loaded then the defaults will have to be used.