@pandeiro: I think that's worth reporting to cask

Does that form throw any errors when you evaluate it manually?

@arrdem: C-c C-k doesn't trigger an overlay because that's not really an eval operation. That's a load-file operation. (They're similar, but different)

@arrdem: But I have the same question as bozhidar, do you really care about the return value of the last sexp when you're loading the entire file?

@luxbock: You can use two nested dolists 😛, but other than that, no

@malabarba: that’s an nREPL implementation detail

the behaviour is different for piggieback

@bozhidar: still, the point is that they're different things for cider.el. We could certainly hide that implementation detail and make C-c C-k create an overlay at the line the cursor is on. That's what M-x cider-run does, for instance.

I never care about the return value of C-c C-k

and the only time I benefited from it was I had done that track-eval hack, which converted evaluations into load-buffer ops

but as this is not working the same way in ClojureScript it’s no longer used anywhere

I think the bigger issue at hand is that many users don’t really understand how they are supposed to interact with cider

I remember I was similarly frustrated way back, when I was starting out with SLIME

we simply have 0 workflow documentation

0 workflow screencasts, etc

@arrdem: why do you need a result overlay with C-c C-k?

@malabarba: thanks; i didn't think it was a cask issue but now that I see @bozhidar's response, I'm wondering...