Re: [go-nuts] Tooling experience feedback

2016-10-28 Thread Mathieu Lonjaret
ah, good to know, thanks. However, it is not something one immediately finds out just by looking at the output of "go help". Afaics, "go doc go" isn't even mentioned (as an example or otherwise) in "go help doc". On 27 October 2016 at 17:56, Russ Cox wrote: > FWIW 'go help all' is essentially 'g

Re: [go-nuts] Tooling experience feedback

2016-10-27 Thread Edward Muller
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 wrote: > FWIW 'go help all' is essentially '

Re: [go-nuts] Tooling experience feedback

2016-10-27 Thread Russ Cox
FWIW 'go help all' is essentially 'go doc go'. On Fri, Oct 21, 2016 at 9:46 AM Mathieu Lonjaret 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

Re: [go-nuts] Tooling experience feedback

2016-10-21 Thread Mathieu Lonjaret
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 w

Re: [go-nuts] Tooling experience feedback

2016-10-18 Thread 'Jaana Burcu Dogan' via golang-nuts
On Tue, Oct 18, 2016 at 12:34 PM, Jan Mercl <0xj...@gmail.com> wrote: > > On Tue, Oct 18, 2016 at 8:54 PM 'Jaana Burcu Dogan' via golang-nuts < > golang-nuts@googlegroups.com> wrote: > > The go tool already does a lot of things, perhaps too much of them. > Please contribute with specific items. H

Re: [go-nuts] Tooling experience feedback

2016-10-18 Thread Jan Mercl
On Tue, Oct 18, 2016 at 8:54 PM 'Jaana Burcu Dogan' via golang-nuts < golang-nuts@googlegroups.com> wrote: The go tool already does a lot of things, perhaps too much of them. The observation that newcomers have trouble to use it to their advantage is both correct and the evidence of its complexity

[go-nuts] Tooling experience feedback

2016-10-18 Thread 'Jaana Burcu Dogan' via golang-nuts
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. T