Closed relatedcode closed 10 years ago
In theory it’s a good idea, but due to this issue I̶ ̶d̶o̶n̶’̶t̶ ̶t̶h̶i̶n̶k̶ ̶w̶e̶ ̶s̶h̶o̶u̶l̶d̶ we should not advocate it at this moment. It would probably be safer once we have prebuilt versions of the xcodeproj gem.
From later in the issue:
I've just tried removing "-V" / "--verbose" and it worked ! thanks @samalone
Hrm, though it did work for me, considering how much stuff is outputted in verbose mode I'd probably say that it's better to show less here.
We should probably just address the real problem, which is that newcomers have no idea how long it should take and assume that it’s not working if it takes too long.
How about adding something like the following?
“Depending on your connection this might take a while. Unless an error is reported let it run its course.”
Hrm, though it did work for me, considering how much stuff is outputted in verbose mode I'd probably say that it's better to show less here.
Indeed. We also don’t want users to miss the changelog we print after a gem install and the amount of noise printed by -V
makes it too easy to gloss over it.
Agreed to all of this. We'll do better to set user expectations rather than to try and make rubygems more verbose, thanks for bringing this up @relatedcode - closing as I've moved this copy into the new guides, and I'll be using that as a reference on the new site.
thanks for bringing this up @relatedcode
Indeed. Thanks a lot for taking the time to provide us with feedback that many would find so obvious and thus is being glossed over. :+1:
I think this is a good idea :+1: