Fork me on GitHub
#cider
<
2023-10-03
>
magnars09:10:11

I see that in a fairly recent CIDER update there has been a change to only popping up the stacktrace-buffer for runtime errors. This makes some sense, since popping up the big stacktrace-buffer isn't necessary for things like syntax errors, but I apparently need help writing code that compiles at times, and now the error message is only found in the REPL buffer. Is there some way to show me the error in the minibuffer, perhaps?

magnars10:10:38

oh, nice! Cheers, @UFAP0C8KU 🙏

👍 1
magnars10:10:21

I'm on CIDER 1.8.0-snapshot <tel:202310011157|20231001.1157> on melpa, and not seeing the red overlay that is supposed to take the place of the stacktrace buffer. I'm triggering a syntax error to verify the behavior. I get the message only in the repl. Where can I start to investigate what is going on?

magnars11:10:27

More information: I get the red overlay when running cider-eval-last-sexp , but not when running cider-load-buffer .

magnars11:10:38

This seems more like a different use case for me. I've asked in the relevant issue. https://github.com/clojure-emacs/cider/issues/3487

👍 1
daveliepmann07:10:47

Thanks for reporting, I'm not yet on this version but this is part of my workflow too