Error message loop when rebel-readline-nrepl looses nrepl server connection

Thanks for a nrepl version of rebel-readline! :) I've been a happy user of rebel-readline for long time, this is a nice addition :) Not sure if it is too early for reports like these, but decided to send one :D Seems that if the nrepl server is killed, the rebel-readline-nrepl clients gets a flood of error messages like these: ``` user=> Execution error (SocketException) at nrepl.transport/bencode$fn$fn (transport.clj:130). The transport's socket appears to have lost its connection to the nREPL server Internal REPL Error: this shouldn't happen. :repl/*e for stacktrace user=> Execution error (SocketException) at nrepl.transport/bencode$fn$fn (transport.clj:130). The transport's socket appears to have lost its connection to the nREPL server Internal REPL Error: this shouldn't happen. :repl/*e for stacktrace ``` Hitting CTRL+C ends the flood though. Just wanted to do a quick friendly report, otherwise rebel-readline-nrepl seem to work nicely :)