.log() to support logging levels about gulp-util

[yocontra]

I think this goes against streams though. If there is an error you are supposed to emit it from the stream which will fail/stop everything involved and throw it (unless a handler is registered).

[robrich]

I agree. gutil.log() is for ancillary content, and errors should be passed down-stream. All the more reason for gulp.silent or similar. I'll think about how best to describe this in README.md.

[yocontra]

@robrich gulp.silent got removed but I didn't replace it... hmm. I might just make gulp.log respect --silent on the CLI but that doesn't feel right. Maybe I should do something like TJs debug and let you silence certain plugins

[robrich]

I like the CLI option (agree, doesn't quite feel right), but I'd like a code-based option too.

[sindresorhus]

My take on it:

• .log: normal logging
• .warn: for warning. yellow color.
• .fail: for things that should stop the build. red color.
• .verbose: for things that shouldn't usually be visible, but can be toggled with the --verbose cli flag. gray color.

This is important to get a consistent logging output from gulp when using multiple plugins.

You might want to look into prolog by @cowboy.

[yocontra]

Consolidating to #33