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.
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
-gocommand will install thegodoc-binary to$GOROOT/bin(or$GOBIN) and the -coverandvetbinaries to -$GOROOT/pkg/tool/$GOOS_$GOARCH. -You can access the latter commands with -"gotoolcover" and -"gotoolvet". -Community resources