We have so many Makefiles that encode $(go list ./... | grep -v vendor) in
one way or another it IS kind of funny. A `novendor` flag of some sort to
most tools that take package specs would be so so so so nice.
On Thu, Oct 27, 2016 at 8:56 AM Russ Cox <r...@golang.org> wrote:
> FWIW 'go help all' is essentially 'go doc go'.
>
> On Fri, Oct 21, 2016 at 9:46 AM Mathieu Lonjaret <
> mathieu.lonja...@gmail.com> wrote:
>
> As you said, sometimes one is not sure in which X for "go help X" one
> might find the information they're looking for. So one can end up
> trying several of them before finding the relevant info. I can think
> of one way that would alleviate that pain a bit: something like a "go
> help all" command that would print all the topics in one go. Makes it
> easier to pipe it to grep/less and search for specific things.
>
>
> On 18 October 2016 at 20:54, 'Jaana Burcu Dogan' via golang-nuts
> <golang-nuts@googlegroups.com> 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.
>
> --
> 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.
>
> --
> 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.
>
--
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.
