This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-22
Channels
- # aatree (2)
- # beginners (14)
- # boot (190)
- # cider (16)
- # cljs-dev (15)
- # cljsjs (6)
- # cljsrn (7)
- # clojure (101)
- # clojure-austin (26)
- # clojure-berlin (2)
- # clojure-estonia (4)
- # clojure-greece (53)
- # clojure-russia (46)
- # clojurescript (44)
- # core-async (12)
- # cursive (57)
- # data-science (49)
- # datomic (5)
- # emacs (8)
- # hoplon (92)
- # ldnclj (20)
- # lein-figwheel (22)
- # leiningen (4)
- # mount (37)
- # om (103)
- # onyx (26)
- # parinfer (70)
- # proton (6)
- # re-frame (32)
- # reagent (1)
- # yada (24)
I just found about cider C-c C-d C-f
to search through clojure docstrings. Amazing !
Even more amazing is that you can then jump to the source insure Clojure. Is that only for Clojure, or is it something I can use as well in my projects (if so how ? ).
Note: I'm using prelude
jump to source should work for ur project and ur dependencies as well. For clj at least. I guess for java deps I need source jars too
If I have a macro in a .cljc
that I refer into a .cljs
file (using :refer-macros
). When placing point on the macro invocation symbol, I get an exception trace from cljs-tooling in the REPL (and the REPL buffer grabs focus), saying the macro’s namespace is not found. This only seems to happen when the macro expands to another macro invocation. Has anyone else noticed this?