gco / rubyripper

Automatically exported from code.google.com/p/rubyripper
0 stars 0 forks source link

Question is shown not until answer is givven on cli #474

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
If you start rubyripper-cli with a cd that has no cddb entry. rubyripper will 
ask if you want to change settings. On my machine, it waits with printing this 
question until I hit enter. But then it's too late...

It looks like there is some output buffer for STDOUT. The problem can be solved 
by adding

STDOUT.flush

after each call to STDOUT.print.

Original issue reported on code.google.com by but...@freenet.de on 17 Sep 2011 at 3:55

GoogleCodeExporter commented 9 years ago
I've spend quite some attention to the CLI lately. I've tested current code 
with an unknown disc and the problem does no longer occur. (Notice that ripping 
is still broken currently).

Original comment by boukewou...@gmail.com on 24 Sep 2011 at 9:04