This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-19
Channels
- # aws-lambda (1)
- # bangalore-clj (4)
- # beginners (66)
- # boot (13)
- # cider (9)
- # cljs-dev (44)
- # cljsjs (3)
- # clojure (181)
- # clojure-austin (2)
- # clojure-greece (6)
- # clojure-italy (2)
- # clojure-russia (64)
- # clojure-sg (1)
- # clojure-spec (68)
- # clojure-uk (60)
- # clojurescript (66)
- # conf-proposals (12)
- # cryogen (1)
- # cursive (3)
- # datomic (44)
- # graphql (1)
- # hoplon (2)
- # jobs (2)
- # jobs-discuss (3)
- # keechma (2)
- # liberator (6)
- # luminus (2)
- # nyc (1)
- # off-topic (92)
- # om (10)
- # onyx (17)
- # parinfer (39)
- # pedestal (8)
- # proton (11)
- # re-frame (110)
- # reagent (2)
- # remote-jobs (11)
- # ring-swagger (9)
- # rum (2)
- # sql (2)
- # test-check (6)
- # untangled (138)
@dpsutton Thanks.
Generic question, how would folks here envision displaying specs of function arguments? Eldoc is already overcrowded ..
Same could be applied to inf-clojure
Don't remember whether eldoc shows params incrementally (if I am writing the second show me the second) but if it does, maybe small specs can fit quite nicely there and a key binding could jump to the s/def
cider-debug-defun-at-point
yields a stack trace and “no reader function for tag dbg”… what do I do?
Google knew the answer:
(#'clojure.core/load-data-readers)
(set! *data-readers* (.getRawRoot #'*data-readers*))
from the discussion in this issue, https://github.com/clojure-emacs/cider/issues/1462
@gonewest818 there should even be a task for doing that (maybe overkill though)
Cool. I'm actually using lein (and circularly, debugging a feature I'm proposing for leiningen) but yes I saw some mention of a boot task for this.