Might it be possible to turn off code fencing entirely, so that the output is just the output?

It’s possible, but I’m always on the fence (sorry) against settings if I can avoid them. Since we are planning to add more output destinations, that won’t call for fencing, this will probably be how we cater to this issue.

I appreciate avoiding settings, and especially that you are keeping your eye on the long game! FWIW though, "the output is the output" would seem to me to be the nicest default behavior.

That’s a thing with avoiding settings. People will have different opinions on what’s nicest. I think it’s nicer with syntax highlighted results than with plain text.

Yes, and understood. FWIW I think my bias is rooted in a love of homoiconicity, or something like that. Lots of my workflows feed printed output and/or returned results back into Clojure as code and/or data, and cluttering it up with extraneous stuff seems like a violation.

Gotcha. There is a command for copying the last result to the clipboard. Sounds like that would fit your workflow? No code fencing or anything like that copied, cross my heart and hope to die.

Thanks! I could see that being helpful, but not the answer if you want a lot of results rather than just the last one. For the moment I've switched to using a mix of Calva for editing and testing small things and the CLI for actually running my main processes, since that sends printed output and results unadulterated to my Terminal window. Possibly I'll stick to something like this going forward, which may be fine.

We’ll see how you like the next output destination options.

Would you like an option to have the evaluated expression printed, btw?

No, I don't think so. My ideal is that all that shows up in the output is things that I explicitly print with println or the like, along with results of expressions that I evaluate with option-return. All unadulterated.

A new Calva is out.

This is amazing! Is it possible to add an optional dependency on clj-commons.pretty to make the default errors more human readable?

What we could do is to check if there are already ansi escapes in the output and skip adding any in that case. Then if you are using whatever in your project, the terminal output will honor it.