Colorized output by default will make for messy logs that can't be used. Sure you can turn it off (with an integer, why not a bool?), but that shouldn't be something compiled in your program. Also there are no means to `printf` strings from the logger.

Finally, there are already a plethora of loggers for Go. I'd recommend logrus for structured logs:

https://github.com/Sirupsen/logrus

Or glog otherwise.

And a note: a logger isn't a debugger. GDB is a debugger for Go, see https://golang.org/doc/gdb

Sorry if I come across as heartless, it's nice to see new people coming to Go. But I don't think this is novel or news worthy.

A wise gopher would use Rob Pikes glog package instead https://github.com/golang/glog

I've been trying to find a small logger program for Go and haven't had time to write my own. Looks great and may start using it :)

The one minor issue is there is a syntax error in the readme. Should be import "github.com/apsdehal/go-logger", not "go get github.com/apsdehal/go-logger"

This looks interesting - I'll take a closer look.

You might want to check out the logrus package - which I'm using and pretty happy with. https://github.com/sirupsen/logrus

Logrus lets you add structured k,v fields so you do have to mess around with fmt and also has hooks to support things like sending logs to syslog or remote exception handling services.

Does this only output to stdout? It would be useful if it took an io.Writer so you could write to a file or something else, too.

Btw, anyone interested in loggers should check out my log rolling package gopkg.in/natefinch/lumberjack.v2

It's a shame there's no basic interface in the go's log package.

package =/= repo name

Don't do that