Bozhidar Batsov

I intentionally made a lot of those buffers generic to avoid the complexity of having them be project-specific. It didn't seem to me transient buffers like results, docs and so...

My bad. They were removed in 0.7, but here you can see how things used to look before - https://github.com/clojure-emacs/cider/blob/fd14211dfe6fa43c951567accb732b549af3ec18/cider-interaction.el#L563 To avoid having to load code in such a horrible...

Yeah, potentially. We'll see what makes sense and what doesn't. I don't want to go overboard with this and for some things the UI will likely be different (e.g. just...

4/5 items are done even now (I've added more functionality to nREPL to account for this). We're just missing a simple eval-based test-runner. (no bells and whistles, just some output...

See https://metaredux.com/posts/2020/06/15/nrepl-0-8-evolving-the-protocol.html

Yeah, that's exactly what I had in mind. And we were doing in the legacy `clojure-test-mode` project (see https://github.com/clojure-emacs/clojure-mode/blob/92f813c4fdd6f124a79f22a1848e15e22e0714a6/clojure-test-mode.el) that was replaced by the `test` middleware.

It'd be good to cover this behavior with some tests, as even I'm struggling a bit to understand what exactly is the edge case we're tackling here.

ping :-)

I'm on the fence about the second version, as then I'd probably need extract a function `cider--goto-prev-expression-start` as well, plus I'm not sure how much overhead the checking for any...

If you disable streamed printing or increase the size of the result chunks this will work as it does in `lein repl`. The problem with chunked output is that it...