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

Jump to bottom

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

Closed
oddlittlebird opened this issue Oct 2, 2020 · 6 comments
Closed

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

oddlittlebird opened this issue Oct 2, 2020 · 6 comments
Labels
Documentation FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Unreleased

Comments

@oddlittlebird
Copy link

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
Member

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

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

@beoran
Copy link

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

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

@dmitshur dmitshur added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Oct 6, 2020
@dmitshur
Copy link
Contributor

dmitshur commented Oct 6, 2020 •
edited

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
@seankhliao
Copy link
Member

This was fixed in CL 297531

@golang golang locked and limited conversation to collaborators Dec 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Documentation FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
6 participants
@beoran @networkimprov @dmitshur @gopherbot @seankhliao @oddlittlebird