Hi Timothy, Glad you liked it! :-) > The only thing I'm wondering, is if the debugger has: > a step into function
Not yet. :-( For now, you can instrument in advance the function you want to step into. > ability to set a break point in a 3rd party lib (where you can't put #break or #debug) This should be working. What I always do is visit the function in question with `cider-find-var` and then just instrument it with the usual command `C-u C-M-x`. If you want to instrument it using the reader macros (#break and #dbg) you can do that too. Just issue `M-x read-only-mode` to disable readonly-ness and treat this buffer like a regular file. > a way to continue to next break point (right now, continue just leaves the current break and completes execution, without stopping on other breakpoints) Could you clarify what you mean by this? You can step to the next breakpoint with n, but I'm guessing that's not what you want. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
