This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-24
Channels
- # adventofcode (33)
- # beginners (15)
- # cider (6)
- # clara (24)
- # cljs-dev (3)
- # clojure (39)
- # clojure-france (1)
- # clojure-greece (1)
- # clojure-norway (1)
- # clojure-spec (9)
- # clojure-uk (1)
- # clojurescript (40)
- # defnpodcast (1)
- # fulcro (9)
- # hoplon (33)
- # jobs-discuss (4)
- # lumo (3)
- # off-topic (4)
- # onyx (2)
- # parinfer (7)
- # precept (45)
- # re-frame (25)
- # ring-swagger (4)
- # shadow-cljs (2)
- # specter (3)
- # sql (10)
- # uncomplicate (3)
- # unrepl (8)
hi, it seems that the cider debugger can only print locals for the current top (or bottom depending on your view) of the call stack. is there any way to get at the values of locals some frames below (or above) that one?
hmm, do you know if it is possible to edit library code (in this case alpha.clj from clojure.spec) to insert a breakpoint at those earlier frames? [the buffer that popped open in emacs after running cider-doc and clicking the link to view source is read-only]. is there another way to edit this library code?
@U0E98NQG2 Why not just use cider-debug-defun-at-point?
Moreover, if you want to modify source of 3rd party code, you can navigate to the source, disable read-only mode (e.g. C-x C-q) and then modify source code and re-eval.