diff --git a/doc/cmd.html b/doc/cmd.html index c590f4d3ec..e30684793a 100644 --- a/doc/cmd.html +++ b/doc/cmd.html @@ -18,10 +18,8 @@ underlying binary with arguments appropriate to package-level processing.

The programs can also be run as stand-alone binaries, with unmodified arguments, -using the go tool subcommand, such as go tool vet. -This style of invocation allows, for instance, checking a single source file -rather than an entire package: go tool vet myprogram.go as -compared to go vet mypackage. +using the go tool subcommand, such as go tool cgo. +For most commands this is mainly useful for debugging. Some of the commands, such as pprof, are accessible only through the go tool subcommand.

@@ -76,7 +74,7 @@ and rewrites them to use newer ones. -fmt +fmt      Fmt formats Go packages, it is also available as an independent gofmt command with more general options. diff --git a/doc/install-source.html b/doc/install-source.html index 6d416d33f1..bbe7cdfd00 100644 --- a/doc/install-source.html +++ b/doc/install-source.html @@ -349,15 +349,7 @@ provides essential setup instructions for using the Go tools.

The source code for several Go tools (including godoc) is kept in the go.tools repository. -To install all of them, run the go get command: -

- -
-$ go get golang.org/x/tools/cmd/...
-
- -

-Or if you just want to install a specific command (godoc in this case): +To install one of the tools (godoc in this case):

@@ -374,16 +366,6 @@ You must also have a workspace (GOPATH) set up;
 see How to Write Go Code for the details.
 

-

-Note: The go command will install the godoc -binary to $GOROOT/bin (or $GOBIN) and the -cover and vet binaries to -$GOROOT/pkg/tool/$GOOS_$GOARCH. -You can access the latter commands with -"go tool cover" and -"go tool vet". -

-

Community resources