Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/go: go help mod prints unclear error message on bad mod subcommand #33153

Closed
ALTree opened this issue Jul 17, 2019 · 2 comments
Closed

cmd/go: go help mod prints unclear error message on bad mod subcommand #33153

ALTree opened this issue Jul 17, 2019 · 2 comments
Labels
FrozenDueToAge modules NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@ALTree
Copy link
Member

ALTree commented Jul 17, 2019

$ go version
go version devel +0cadf40f4c Tue Jul 16 22:31:35 2019 +0000 windows/amd64

go help mod prints:

Go mod provides access to operations on modules.

[...]

Use "go help mod <command>" for more information about a command.

go help mod <command> works as advertised, except when <command> is not a valid mod command; in that case this bizarre error message is printed:

$ go help mod bad
go help mod bad: unknown help topic. Run ' mod'.

It's not clear what it means by Run ' mod', but it doesn't look right.

@ALTree ALTree added NeedsFix The path to resolution is known, but the work has not been done. modules labels Jul 17, 2019
@ALTree ALTree added this to the Go1.14 milestone Jul 17, 2019
@gopherbot
Copy link

Change https://golang.org/cl/187217 mentions this issue: cmd/go: Fix the suggested command on the help error message

@jmartin82
Copy link
Contributor

Hi,

This issue is not only affecting mod subcommands, but it's also affecting all of them.

For example:

go help vet a

go help vet a: unknown help topic. Run ' vet'.

I've added a CL with the fix.

@golang golang locked and limited conversation to collaborators Jul 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge modules NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants