This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-05
Channels
- # aatree (2)
- # admin-announcements (15)
- # announcements (2)
- # aws (8)
- # beginners (160)
- # boot (290)
- # braid-chat (28)
- # cider (8)
- # clara (1)
- # cljsrn (3)
- # clojure (154)
- # clojure-czech (7)
- # clojure-russia (162)
- # clojurebridge (2)
- # clojurescript (128)
- # cursive (29)
- # datomic (30)
- # emacs (7)
- # events (1)
- # hoplon (5)
- # jobs (1)
- # ldnclj (7)
- # leiningen (3)
- # off-topic (11)
- # om (82)
- # onyx (68)
- # overtone (1)
- # parinfer (57)
- # portland-or (1)
- # proton (18)
- # re-frame (8)
- # reagent (32)
- # ring-swagger (3)
- # yada (5)
I created a cider
task in my profile.boot
(basically, copied the wiki "better method") and set my cider-boot-parameters
to cider repl -s wait
.
what's weird is, when I first installed cider it pulled 0.11.0-SNAPSHOT, and it complained about being out of sync with 0.10.2. I uninstalled cider, pinned it to melpa-stable
and re-installed. FWIW, I don't get the complaint when running with lein.
Hm, it's probably some small detail in your boot config, but my boot knowledge is nil
If no one else replies here, just open a new issue with full details of your configs and the messages you get. Someone will surely see it there.
@curtosis you can do the whole thing from the command line actually, see https://github.com/clojure-emacs/cider/issues/1531 for details
so this: [boot] -d cider/cider-nrepl:0.10.2 -d org.clojure/tools.nrepl:0.2.12 repl -m cider.nrepl/cider-middleware -s wait
might just do the trick without the task
that actually pointed me to the problem -- somehow I'd missed adding cider-middleware
, which would make sense of the weird symptom (could tell when the versions were out of sync, but couldn't tell when they were in sync). Added in middleware, and everything starts up all nice and quietly. Thanks!