Aborting `rake` execution needlessly dumps a backtrace

[booch]

When aborting rake with Ctrl+C, it outputs rake aborted! then dumps a long backtrace. This seems unnecessary, as aborting isn't really an unexpected outcome of pressing Ctrl+C (or sending an INT signal).

I'd like to propose catching the Interrupt exception and exiting cleanly (with an exit code of 1). We can still print the backtrace if the --trace option is used.

I can submit a pull request, if this seems reasonable.

[SwagDevOps]

Exit code, should be more specific than 1: http://tldp.org/LDP/abs/html/exitcodes.html

sleep infinity
# Ctl-C
echo $?
# 130

[mateusdeap]

Is this something we still want to look at? I can also submit a PR for this if needed.

[SwagDevOps]

Yes! I'm still interested.