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

proposal: go get: add progress bar for downloading #40177

Closed
lolbinarycat opened this issue Jul 12, 2020 · 4 comments
Closed

proposal: go get: add progress bar for downloading #40177

lolbinarycat opened this issue Jul 12, 2020 · 4 comments
Labels
FrozenDueToAge Proposal
Milestone
Proposal

Comments

@lolbinarycat
Copy link

Currently, go get produces no output on a successful install. This can lead to confusion for new programmers, as it is not clear that the command is doing anything, especially if you are used to the like of apt, which will give you a massive wall of text whenever you download something. This is made worse if you are downloading a large package, as it might look like the program has frozen.

I'm not sure if this should be the default behavior or not, as changing the default command output could break scripts. Making it a flag would solve this, but could reduce benefit for new devs.
@gopherbot gopherbot added this to the Proposal milestone Jul 12, 2020
@seankhliao
Copy link
Member

definitely not default, and there is -v for more verbose output/progress

@robpike
Copy link
Contributor

robpike commented Jul 12, 2020

Please no. Let the command continue to run quietly if there's nothing to report.

@ALTree
Copy link
Member

ALTree commented Jul 13, 2020 •
edited

As Rob said, most go commands are quiet by default, and this is unlikely to change. See #22800, #22356, #17959, #18388; in particular #18388 (comment).

Closing this discussion as a dup of the above.

@ALTree ALTree closed this as completed Jul 13, 2020
@lolbinarycat
Copy link
Author

I looked through the issues, and one thing noone seemed to mention is that -v still doesn't output that much. I think an easy compromise would be a flag to pipe the output of sub-commands (e.g. git clone) to stdout. maybe something like -vv?

@golang golang locked and limited conversation to collaborators Jul 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge Proposal
Projects
None yet
Milestone
Proposal
Development

No branches or pull requests
5 participants
@ALTree @robpike @gopherbot @seankhliao @lolbinarycat