On Tuesday, July 12, 2016 at 11:26:57 PM UTC-6, Ian Lance Taylor wrote: > > On Tue, Jul 12, 2016 at 9:36 PM, Zac Pullar-Strecker <zac...@gmail.com > <javascript:>> wrote: > > Commands like go run, go build and go test amoung others should have > > coloured output when an error occurs. it would make reading stack traces > a > > lot easier. I personally use the go run tool a lot during development > > because I have no reason to keep a binary in the $GOPATH/bin directory > when > > it's likely to change in the next 5 minutes. > > > > github.com/fatih/color & github.com/kortschak/ct are os agnostic (Unix > & > > Windows,) packages for ANSI escape codes. > > It would make sense to do this with a flag -c or -color and anyone who > > wanted it perminantly could alias it. > > I'm relatively new to the community so I wanted to post it here before > > creating an issue on github. Are there any issues with doing this? > > I think this is unlikely to be accepted. > > Much more plausible would be a go-gettable colorizing filter that you > can apply to the go tool output. Then you could run a shell script > that pipes go through that filter. > > An example of one that does this for gcc is https://github.com/colorgcc/colorgcc
Damian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
