Clojurians Log v2

with cider and cljr enabled, assuming you have evaled a namespace, isn't their functionality to auto recongnize the namespace by the filename and auto insert the require. E.g if i'm in drewverlee.core and drewverlee.helper contains a fn bar wont typing helper/ in core insert the require statment? i feel like this was happening for me and now its not. but maybe thats wishful thinking.

When cider fails to launch the REPL, an error is displayed in the bottom of the screen. (See screenshot below) but the error is cut. How can I see the full error?

i believe the menu in that window has an "all" option. These are the docs: https://docs.cider.mx/cider/usage/navigating_stacktraces.html

https://github.com/clojure-emacs/clj-refactor.el/wiki/cljr-add-missing-libspec

Put the cursor on the name of a function from a different namespace and , r a m in clojure-mode with the REPL running. If you put the alias you want to use before the function name, , r a m will also add the alias to the require.

i must have had to much to drink last night, i could have sworn it was magically adding the requires to my namespace. 😆

but yes that works

there. it just did it. i didnt run ,ram and it aut filled it. maybe its when there arent clashes.

Perhaps its one of the magic requires you are using... https://github.com/clojure-emacs/clj-refactor.el/wiki#magic-requires

@viebel for that I usually navigate to the messages buffer by doing SPC b b and searching *Messages*. The error can be read more easily from there.

nope. its just a ns i created. ill give this another round then give up. its a bit weird.

ok once you use refactor to include a lib once it will include it automaically past that. it must add it to the magic requires list or something.

scratch that, like the docs say it adds them if you define the alias somewhere else that you have evaled.

Indeed the error is fully logged in the *Messages* buffer

Not sure how to read the error as a stack trace as @drewverlee suggested

as i understand it, cider classifies the ST by a couple categories (clojure, java, repl) and it lets you filter them out:

Show: Project-Only All 
  Hide: Clojure Java REPL Tooling Duplicates  (39 frames hidden)

you can't just scroll down in the buffer?

I can scroll the buffer and read the whole error. Is there a way to navigate errors in *Message* buffer as a stacktrace?

Not that I’m aware of. I’ve always assumed that stacktrace navigation required a running cider REPL, which is why exceptions on start appear in this raw form. No clue if that’s true tho.