don't allow irb to dump output for forever and ever
You've done this before, I know you have. You were screwing around in IRB and you ran something stupid and IRB just started dumping output. LOTS of output. Output that would scroll by for an hour if you don't go kill it. Output going by so fast that it's useless. So much output that your lappy laptop starts burning your knees. (That much output!)
Then, to compound problems, Crtl-C doesn't work here. Maybe you're in some weird context, or on a low-mem server and everything is just... What, Bam, UNRESPONSIVE.
Ugh, the troubles! Now you gotta gotta bust out the 'kill -9' (if you can even get another terminal open) and lose any progress you may have been working on.... OH MAN!
Wouldn't it be nice if IRB limited its output, much the way psql/less do? That is, at some point if enough output has scrolled by, Stop, and let me have the option to continue or not.
That'd be cool.
Updated by Anonymous about 7 years ago
On 06/11/2013 09:41 AM, crankharder (Josh Sharpe) wrote:
Agreed, it would be nice to have LESS(1) functionality in irb.
Have you tried the pry gem? It does behave like less (including regex
If you want to use irb, there is this snippet for your .irbrc (though it
seems incompatible with wirble), which abbreviates long output:
# credit to Stian Haklev
alias initialize_before_max_output_size initialize def initialize(*args) initialize_before_max_output_size(*args) @max_output_size = IRB.conf[:MAX_OUTPUT_SIZE] || 500 end
sprintf @context.return_format, @context.last_value.inspect
sprintf @context.return_format, @context.last_value
max = @context.max_output_size
if text.size < max
puts text[0..max-1] + "..." + text[-2..-1]