I suppose we could overload cider-inspect-last-result to show the stacktrace buffer in case of an error?

conceptually it's the same sort of action - "see more" of the output

@qythium Yeah, that sounds reasonable. I guess there are many places where we don’t handle in a smart manner getting an error instead of a result.

For inspect another option would be to pass the inspector the stacktrace as a raw inspectable datastructure.

@qythium: This has been tried and tested in Calva since start, and it certainly seems to be a good idea. i have also been wanting to make it easy to inspect the error further.