cursive 2019-08-22 | Slack Archive

caleb.macdonaldblack01:08:46

Anyway to get a stack trace of a execution error with a useful stacktrace when sending code to the REPL instead of a syntax error?

caleb.macdonaldblack01:08:15

If I execute the code in the repl I get a reference to the line of the exception

caleb.macdonaldblack01:08:27

When I send to the repl I get a reference to the line of the code I sent to the repl

Lone Ranger02:08:11

Did you try (pst)?

cfleming04:08:09

@caleb.macdonaldblack There’s a “Print stacktrace” button in the REPL toolwindow

dazld20:08:23

is there any way to get clojure data structures in the debugger? I’m having a hard time parsing all the java 😞

souenzzo20:08:20

@U3ZUC5M0R there is some repl-driven solutions, like https://github.com/vvvvalvalval/scope-capture I usually just place a "inline def " then I inspect it in REPL https://blog.michielborkent.nl/2017/05/25/inline-def-debugging/

dazld20:08:15

that’s a fun technique! thanks for the hint

dazld20:08:34

I’ve been doing similar things with atoms and conditions.. pushing stuff when some condition appears

dazld20:08:52

(like breakpoint expressions)

dazld20:08:45

it does work.. ish. cursive is a wonderful place to work, but I do look enviously at things like the cider debugger, or the chrome devtools (for example).

dazld20:08:40

oh! https://groups.google.com/forum/#!topic/cursive/v_gqcKmuNk4

jumar04:08:54

I do use cider daily but, on the other hand, the Cursive debugger is much better when you need to jump around in the stacktrace or debug Java code too

dazld20:08:56

locals etc

2019-08-22

Channels