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

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

Open
oddlittlebird opened this issue Oct 2, 2020 · 5 comments

Comments

@oddlittlebird
Copy link

@oddlittlebird oddlittlebird commented Oct 2, 2020

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.

image

@gopherbot gopherbot added this to the Unreleased milestone Oct 2, 2020
@seankhliao
Copy link
Contributor

@seankhliao seankhliao commented Oct 2, 2020

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
Copy link
Author

@oddlittlebird oddlittlebird commented Oct 2, 2020

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

@beoran
Copy link

@beoran beoran commented Oct 3, 2020

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
Copy link

@networkimprov networkimprov commented Oct 4, 2020

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

@dmitshur
Copy link
Contributor

@dmitshur dmitshur commented Oct 6, 2020

Thanks for the report.

/cc @stevetraut

@dmitshur dmitshur changed the title x/website: x/website: on tutorial/call-module-code page, suggested Windows command may not work if PowerShell is used instead of the Command shell Oct 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants