One tool I add to most of my projects is a Make target that opens documentation for the current project in a web browser.
I wrote a short binary to do this here: https://github.com/kevinburke/godocdoc It would also be nice to be able to jump easily from a bug number, e.g. 17391, to the relevant description, e.g. github.com/golang/go/issues/17391. On Tuesday, October 18, 2016 at 11:54:49 AM UTC-7, Jaana Burcu Dogan wrote: > > Hello gophers, > > I am going to spend some time on improving the not-documented or > hard-to-use parts of the Go tools. I will mainly focus on go build and go > test. The work will consist of reorganizing manuals, proposing new > subcommands or flags to support commonly used multi-step things and so on. > > To give you some concrete examples: > > I have been in cases where users cannot find the build flags because they > are hidden. E.g. > > $ go test -help > test [build/test flags] [packages] [build/test flags & test binary > flags] > ... > > requires you to know about where the build flags are. Some tools are > invisible for the newcomers. > > The other example is about test coverage. It is so tedious that I need an > alias. > > func gocover() { > go test -v -coverprofile=coverage.out && go tool cover > -html=coverage.out > } > > I want to learn more about your experience, aliases, etc to propose > improvements and work on the most commonly suggested items. I also am > planning to go through this mailing list, stack overflow and other channels > to see the common complaints. > > Feel free to reply to this thread or write to me privately. > > Thanks, > JBD > -- 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.
