Don't drop *out* on cider-interactive-eval-print

[gfredericks]

Print *out* to the repl buffer just like in cider-interactive-eval.

I think this is a more common expectation than dropping the *out*. Is there a better way to do this, perhaps so that it's configurable? I pretty much haven't written any elisp ever.

[bbatsov]

I'll have to think about this. Clear the current situation is suboptiomal as we should preserve the output somewhere, but on the other hand it seems odd to send to the REPL output from code that wasn't executed there. I was thinking at some point that maybe we need some extra buffer like cider-output for output generated from interactive evaluations.

[gfredericks]

C-x C-e already does this, right? You evaluate code in the code buffer, the result goes to the minibuffer, but *out* goes to the repl buffer.

This patch actually consists of just copying the code from that codepath.

I don't mind the cider-output idea though.

[bbatsov]

@fredericksgary Yeah, the code you've submitted is OK. I was talking about the more general issue of whether it's a good idea to funnel the output from everything in the REPL buffer. See my last comment in #572.