Supress traceback on Ctrl-C

[Olivia5k]

I've been using kicker to quickly run my tests for well over two years now. It's awesome, but I always slightly twitch a bit whenever I stop the kicking with Ctrl-C. Doing so prints a traceback, and tracebacks are to me the signal that something has gone wrong. In this case, nothing has gone wrong, I'm just stopping the application as I normally do.

My suggestion is to handle Ctrl-C (SIGINT, I guess) and just print a confirmation that kicker will now quit, rather than a lengthy thread traceback.

Very minor thing indeed, but a nice thing to fix nonetheless!
I would've fixed this myself, but my Ruby-fu was a bit too weak for this. I can't imagine it to be very tricky though.

[Manfred]

That's a good point and I fully agree. I'm currently experimenting with a rewrite for version 4 and I will definitely consider your suggestion.