Hey guys, wanted to check what is the state of master.
Right now I'm having some weird failures in test_gem_command_manager.rb:
C:\Users\Luis\Projects\oss\rubygems>ruby -Ilib test\test_gem_command_manager.rb
Test run options: --seed 64614
Loaded suite test/test_gem_command_manager
Started
F.
Please ignore this, stupidity has been raising lately in my brain.
ruby -Ilib;test solve that individual test. will get the real ones
with problems and post again.
--
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing mo
Hello guys,
In case you didn't see the pull request #2:
http://github.com/rubygems/rubygems/pull/2
I wanted to bring it to attention.
Basically the problem is raised due big gems, particularly QtBindings
which Windows binaries weight 49MB and the pure-ruby one is 1.6MB
The problem with such ge
spinner = %w[|/-\]
class << spinner; def next; @s||=0; se...@s]; ensure; @s = @s + 1 == size ? 0 :
@s + 1; end
t = Thread.new do
while true
sleep 0.5
$stdout.sync = true
ui.print "\r#{spinner.next}"
end
end
# when done:
t.kill
seems cheap and portable enough, with a bit
On Sun, Sep 26, 2010 at 11:26 PM, James Tucker wrote:
> spinner = %w[|/-\]
> class << spinner; def next; @s||=0; se...@s]; ensure; @s = @s + 1 == size ? 0
> : @s + 1; end
> t = Thread.new do
> while true
> sleep 0.5
> $stdout.sync = true
> ui.print "\r#{spinner.next}"
> end
>
