Fork me on GitHub
#spacemacs
<
2020-06-14
>
Drew Verlee15:06:32

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.

practicalli-john15:06:46

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.

Drew Verlee16:06:58

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

Drew Verlee16:06:02

but yes that works

Drew Verlee16:06:20

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

Drew Verlee16:06:23

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

Drew Verlee16:06:04

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.

Drew Verlee17:06:34

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

Yehonathan Sharvit15:06:50

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?

practicalli-john16:06:47

In the *cider-error* buffer there are buttons that show and hide information. These buttons are under the top next to the Show: / Hide: labels

Drew Verlee15:06:13

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

cjsauer16:06:46

@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.

jumar06:06:19

You can just SPC b m

Yehonathan Sharvit17:06:52

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

Yehonathan Sharvit17:06:32

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

Drew Verlee18:06:18

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)
it seems to just hide them in the buffer. I assume "more..." indicated some where hidde, but that doesn't seem to be the case.

Drew Verlee18:06:26

you can't just scroll down in the buffer?

Yehonathan Sharvit18:06:25

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

cjsauer21:06:33

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.

practicalli-john16:06:47

In the *cider-error* buffer there are buttons that show and hide information. These buttons are under the top next to the Show: / Hide: labels