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

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

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

we can only try to do more dynamic analysis

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

(or even better - comment there on its importance)

this is related to https://github.com/clojure-emacs/cider-nrepl/issues/64

@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

@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

also

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

may be a bit of help with broken code

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

@arrdem you could throw an exception

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

It won't kill the debug session

And you'll get a regular cider stack trace buffer

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.

huh ok I'll check that out thanks malabarba

You can also file a feature request, of course ☺️

I will 😛

once I get this debugged