pr-values isn't what turns them in to strings

@hiredman are you thinking of bencode?

no

interruptible-eval does

it catches exceptions when evaling and sends them back as the error nrepl message with stirng values

likely the easiest thing to do would be to have your middleware watch for error nrepl messages and then eval *1 to get the error object (before pr-values)

pr-values only applies to the results of normal execution

this is invaluable to me.

Thank you very much

okay, follow up question. I have never seen a :ex keyword in a response, it's always been a string in :err

what makes :err

:err is a message printed to *err* not an exception

:err is like stderr

:out is like stdout

okay, and I have messages coming back with :err, so and no :ex so I did not think it was that simple

you can generate :errs by (binding [*out* *err*] (println "foo"))

and running code can do it at anytime without bubbling up an exception anywhere, or even throwing an exception

yes! this was exactly what I needed. Thank you very much @hiredman