This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-10
Channels
- # aleph (2)
- # arachne (1)
- # beginners (5)
- # boot (33)
- # cider (12)
- # cljs-dev (6)
- # cljsrn (26)
- # clojure (33)
- # clojure-austin (7)
- # clojure-belgium (6)
- # clojure-chicago (1)
- # clojure-dusseldorf (1)
- # clojure-fr (1)
- # clojure-hamburg (1)
- # clojure-nl (11)
- # clojure-portugal (3)
- # clojure-russia (14)
- # clojure-spec (35)
- # clojure-uk (28)
- # clojurescript (49)
- # component (7)
- # core-async (75)
- # cursive (13)
- # datomic (15)
- # dirac (57)
- # emacs (5)
- # events (1)
- # hoplon (34)
- # jobs (2)
- # jobs-discuss (8)
- # lambdaisland (1)
- # lein-figwheel (7)
- # leiningen (3)
- # om (5)
- # onyx (8)
- # re-frame (56)
- # reagent (13)
- # testing (7)
- # untangled (30)
- # vim (51)
- # yada (17)
am i crazy or am i missing the cider messages buffer with all of the traffic between nrepl and cider?
aha. https://github.com/clojure-emacs/cider/commit/360daba09dc32d9f6208fac105285f5c8f3aed6c
yeah, it was recently disabled by default as some people were reporting that logging was slowing down CIDER for them
as for the previous conversation - it might be good to add a section “Hacking on CIDER” or something like this to the manual
CIDER already highlights calls to functions marked as ^:deprecated
which is very nice. I wonder how to make it mark any arbitrary metadata? In my case, we have a lot of functions marked with ^:io
and it would be great to have them be highlighted in CIDER.
@bozhidar I added a placeholder issue about adding hacking to the cider docs: https://github.com/clojure-emacs/cider/issues/1862
@codemartin It’s doable, but might require some changes to the code, to be extensible
not sure if we didn’t hardcore the supported metadata in the middleware or something like this
@bozhidar That might just be my first code contribution to CIDER. Thanks!