Clojurians Log v2

Compile-time errors (and read-time ones, like in this case) by default don't bring forward the error buffer. We assume that the inline error message should be enough to understand the issue + we highlight the problematic part when possible. In this case, obviously, the information was not sufficient to debug. I will investigate how we can improve the inline error message for this case; however, you can also disable this behavior by customizing cider-clojure-compilation-error-phases, see https://docs.cider.mx/cider/usage/dealing_with_errors.html#configuration

361

But also, when this happens, you can type *e in the repl, and see the stacktrace, which will have line numbers in it.

Thanks, @hhausman

Looks like I can also do C-x b **cider-error** . It didn't pull up the error buffer automatically, but it sure enough populates it with the stacktrace