Yeah that seems like unexpected behavior.  I guess ctrl-c is being by 
default passed to the subprocess.  In my experience ctrl-c is either 
passed to any currently 'being run' subprocess, OR to Ruby (like begin 
... rescue Interrupt...end) but not to both, which happens here.  Odd, I 
agree.

-Roger
-- 
Posted via http://www.ruby-forum.com/.