This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-04
Channels
- # aleph (2)
- # beginners (80)
- # boot (18)
- # cider (6)
- # cljs-dev (14)
- # cljsrn (5)
- # clojure (114)
- # clojure-android (5)
- # clojure-dev (8)
- # clojure-greece (6)
- # clojure-italy (9)
- # clojure-russia (108)
- # clojure-uk (82)
- # clojurescript (158)
- # css (1)
- # cursive (21)
- # data-science (1)
- # datomic (66)
- # emacs (9)
- # ethereum (3)
- # fulcro (26)
- # graphql (7)
- # hoplon (25)
- # juxt (2)
- # keechma (34)
- # lein-figwheel (4)
- # leiningen (2)
- # off-topic (4)
- # om (5)
- # onyx (14)
- # parinfer (2)
- # pedestal (17)
- # planck (3)
- # portkey (14)
- # re-frame (23)
- # reagent (12)
- # ring (8)
- # rum (1)
- # shadow-cljs (506)
- # spacemacs (2)
- # vim (11)
- # yada (6)
i'm using the cider debugger to debug a large function, but i'm only interested in a few parts, is there a way to mark expressions so that the debugger always skips there?
Something like this:
(let [not-interesting ^:no-dbg (skip-this ...) interesting (will-break ...)] ....)
@chrisblom you can alway use h
to jump to force the debugger to stop on the cursor point.
anyway, i'm now annotating just the parts i want with #dbg
instead of marking the whole function, and what does the trick for new
Hi channel. Can anyone tell me if it is possible to get better test diffs in emacs cider?