x/website: on tutorial/call-module-code page, suggested Windows command may not work if PowerShell is used instead of the Command shell

[oddlittlebird]

This is an issue on https://golang.org/doc/tutorial/call-module-code, the last step.

I am running the current version of Go on my Windows 10 machine. I accidentally ran the Linux command, and I got the result you said I should. When I ran the Windows command, I got something completely different. I have no idea where that text came from.

Please update your tutorial.

[seankhliao]

were you running other tutorials/examples before? like this section https://golang.org/doc/gopath_code.html#remote references an example program at github.com/golang/example/hello called hello with that output

[oddlittlebird]

I did the Getting Started tutorial, that's it. I literally started Go today with the golang.org tutorials.

[beoran]

I assume that there are two hello binaries on your machine, where hello.exe is somewhere in your shell path %PATH%. I think that if you give the command .\hello.exe you should get hello.exe in that directory to run. Then look around in your path for the second hello.exe, and perhaps delete it if it bothers you.

[networkimprov]

Note that you're using PowerShell, and the instructions are written for the Command shell.

[dmitshur]

Thanks for the report.

/cc @stevetraut

[seankhliao]

This was fixed in CL 297531