cmd/go: clarify that tag lists are space-separated

Apparently the current documentation is confusing users that
quickly skim the flags list at the top. Make very clear that
build tags are space-separated.

Updates #18800

Change-Id: I473552c5a2b70ca03d8bbbd2c76805f7f82b49a2
Reviewed-on: https://go-review.googlesource.com/35951
Reviewed-by: Daniel Martí <mvdan@mvdan.cc>
Reviewed-by: Minux Ma <minux@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>

diff --git a/src/cmd/go/alldocs.go b/src/cmd/go/alldocs.go
index 3d5dd2b39725883fd01bb5541d8604c268ddd4fc..5b768900b1cf608f9be8ed1d7168b5020bb44156 100644 (file)
--- a/src/cmd/go/alldocs.go
+++ b/src/cmd/go/alldocs.go
@@ -131,16 +131,17 @@
 //             For example, when building with a non-standard configuration,
 //             use -pkgdir to keep generated packages in a separate location.
 //     -tags 'tag list'
-//             a list of build tags to consider satisfied during the build.
-//             For more information about build tags, see the description of
+//             a space-separated list of build tags to consider satisfied during the
+//             build. For more information about build tags, see the description of
 //             build constraints in the documentation for the go/build package.
 //     -toolexec 'cmd args'
 //             a program to use to invoke toolchain programs like vet and asm.
 //             For example, instead of running asm, the go command will run
 //             'cmd args /path/to/asm <arguments for asm>'.
 //
-// The list flags accept a space-separated list of strings. To embed spaces
-// in an element in the list, surround it with either single or double quotes.
+// All the flags that take a list of arguments accept a space-separated
+// list of strings. To embed spaces in an element in the list, surround
+// it with either single or double quotes.
 //
 // For more about specifying packages, see 'go help packages'.
 // For more about where packages and binaries are installed,

diff --git a/src/cmd/go/internal/work/build.go b/src/cmd/go/internal/work/build.go
index 06611885dac979614dcf4b23a1c0313231a90779..2ed4d6b6ec28a73e4711b3095cb58179e4daaa52 100644 (file)
--- a/src/cmd/go/internal/work/build.go
+++ b/src/cmd/go/internal/work/build.go
@@ -116,16 +116,17 @@ and test commands:
                For example, when building with a non-standard configuration,
                use -pkgdir to keep generated packages in a separate location.
        -tags 'tag list'
-               a list of build tags to consider satisfied during the build.
-               For more information about build tags, see the description of
+               a space-separated list of build tags to consider satisfied during the
+               build. For more information about build tags, see the description of
                build constraints in the documentation for the go/build package.
        -toolexec 'cmd args'
                a program to use to invoke toolchain programs like vet and asm.
                For example, instead of running asm, the go command will run
                'cmd args /path/to/asm <arguments for asm>'.
 
-The list flags accept a space-separated list of strings. To embed spaces
-in an element in the list, surround it with either single or double quotes.
+All the flags that take a list of arguments accept a space-separated
+list of strings. To embed spaces in an element in the list, surround
+it with either single or double quotes.
 
 For more about specifying packages, see 'go help packages'.
 For more about where packages and binaries are installed,