This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-06-15
Channels
- # admin-announcements (90)
- # beginners (36)
- # boot (169)
- # cider (18)
- # clojure (84)
- # clojure-australia (1)
- # clojure-brasil (20)
- # clojure-czech (2)
- # clojure-france (5)
- # clojure-germany (1)
- # clojure-india (8)
- # clojure-italy (39)
- # clojure-japan (14)
- # clojure-korea (2)
- # clojure-russia (9)
- # clojure-sg (1)
- # clojure-spain (16)
- # clojure-ukraine (1)
- # clojurebridge (20)
- # clojurescript (146)
- # code-reviews (48)
- # core-typed (1)
- # datomic (24)
- # editors (59)
- # euroclojure (6)
- # ldnclj (25)
- # off-topic (6)
- # onyx (3)
- # reagent (7)
@bentanweihao: cider-refresh
does what’s outlined here http://thinkrelevance.com/blog/2013/06/04/clojure-workflow-reloaded
@bozhidar: I shouldn’t have to explicitly call cider-mode
in the clojure-mode-hook
, right? For some reason in the last couple of weeks, I’ve had to do that explicitly
I have a feeling that something else is afoot, though, because occasionally my other hooks (paredit and rainbow delimiters) also don’t get called
cider inserts a hook for clojure-mode
automatically the first time you use it to connect
this used to Just Work, and I’m sure it still does. I’ll need to spend some time paring down my config to see if something else is causing the new regression