Fork me on GitHub
#cider
<
2015-12-15
>
bozhidar06:12:54

@cichli: the parser evaluates all code to generate the AST, which causes the problems you mentioned

bozhidar06:12:35

this is the prime reason I opted not to use it in cider itself

bozhidar06:12:59

the problem is that this has no real alternative in terms of precise static analysis

bozhidar06:12:11

we can only try to do more dynamic analysis

bozhidar06:12:20

can I ask everyone here to take a minute to upvote this ticket http://dev.clojure.org/jira/browse/CLJ-1161

bozhidar06:12:33

(or even better - comment there on its importance)

benedek12:12:58

@cichli the protocol issue should be fixed in the latest 2.0.0 snapshot with this https://github.com/clojure-emacs/refactor-nrepl/issues/126

benedek13:12:09

@jonpither (setq cljr--debug-mode t) tells u when the AST index gets updated and also more detailed clj-refactor error traces if u suspect it

benedek13:12:15

also

;; use find usages even if stuff is broken
(setq cljr-ignore-analyzer-errors t)

benedek13:12:43

may be a bit of help with broken code

arrdem20:12:30

Is there a way with CIDER defn debugging to show the stack?

malabarba22:12:52

@arrdem you could throw an exception

malabarba22:12:37

Press e, type in (throw (Exception. "hi")), and hit RET.

malabarba22:12:57

It won't kill the debug session

malabarba22:12:20

And you'll get a regular cider stack trace buffer

malabarba22:12:23

I remember briefly looking into a proper way of showing the stack. But then I realised you can just throw an exception and I got diverted by other features.

arrdem22:12:45

huh ok I'll check that out thanks malabarba

malabarba22:12:54

You can also file a feature request, of course :relaxed:

arrdem22:12:02

I will 😛

arrdem22:12:09

once I get this debugged