cider

bolivier 2025-11-06T13:25:14.719059Z

Is there a way to always send evaluated results to the cider-resultbuffer? I didn't see anything in the code that seemed like it would make that easy.

oyakushev 2025-11-06T14:22:11.433269Z

There is cider-eval-last-sexp-to-repl. Isn't it what you need?

bolivier 2025-11-06T14:24:19.778839Z

I tend to almost always use cider-pprint-eval-last-sexp cause I like seeing the result in a full buffer instead of the minibuffer (I sometimes keep it open in a dedicated new frame). But I would like to be able to use stuff like cider-eval-last-sexp-in-context and also have that sent to the *cider-result* buffer, but I'm not sure how to do that.

oyakushev 2025-11-06T14:25:30.786889Z

Yeah, you would need to combine two functions somehow. This is not available OOTB.

jumar 2025-11-06T19:50:27.155139Z

Could you use cider-inspect* commands? That opens *cider-inspect* buffer which is refreshed every time you evaluate a new value.