logformat enhancement about log15 HOT 2 OPEN

Interesting idea. Have you seen the discussion on issue #14?

I'm on the fence here. On the one hand TerminalFormat is documented as not recommended for production uses because it isn't as machine parsable as other formats, so giving the developer some control seems reasonable. On the other hand it goes against log15's opinion that we should prefer machine parsable log formats.

If we did include a format like this in log15 we would prefer to create a new format rather than breaking the v2 API by changing the existing TerminalFormat.

from log15.

I looked at #14 and I agree that machine parsable code is far better to store historical data, that said watching an os.StdOut dump visually is far easier if we can specify the order. For example in my web application the logger will always have the ip, module and controller in the log context so I would like to be able to specify for the terminal output those items first, then the message then any other context.

And I am ok with a new Formatter implementing this.

from log15.