This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-26
Channels
- # aws-lambda (2)
- # beginners (10)
- # boot (17)
- # cider (19)
- # clara (1)
- # cljs-dev (13)
- # cljsjs (22)
- # cljsrn (1)
- # clojure (132)
- # clojure-austin (2)
- # clojure-berlin (2)
- # clojure-dusseldorf (1)
- # clojure-germany (2)
- # clojure-italy (7)
- # clojure-spec (6)
- # clojure-uk (5)
- # clojurescript (45)
- # core-matrix (3)
- # cursive (4)
- # datomic (8)
- # emacs (3)
- # keechma (3)
- # lein-figwheel (1)
- # leiningen (2)
- # lumo (24)
- # nyc (1)
- # off-topic (29)
- # om (68)
- # onyx (5)
- # perun (50)
- # planck (5)
- # protorepl (5)
- # re-frame (128)
- # reagent (10)
- # remote-jobs (1)
- # ring (4)
- # rum (41)
- # untangled (28)
- # yada (4)
seems to me we could have made the problem easier to spot if the message included some details about the connection endpoint
@bozhidar or just use 127.0.0.1?
@pesterhazy that'll break systems which don't have ipv4
is that a practical possibility?
I've never heard of such a desktop system
i'm not using any linux desktop systems at all, and i've seen servers without ipv4 in the real world.
i'm not saying that using 127.0.0.1 is not a practical solution, but it is not a good solution in the longer run.
the proper solution seems for the nREPL server to listen to ::1
as well as 127.0.0.1
also cider could use localhost
but prefer ipv4 if available
when I do do a cider-jack-in-clojurescript and I have two repls
with C-c C-z
I always switch to the clojurescript one
no way to switch to the clojure repl?
I mean I can just switch buffer of course
@andrea.crotti iirc it chooses based on the mode, so cljs to cljs repl. Some var controls the behavior of cljc files, but I can't recall which one.
ah yes you're right actually @richiardiandrea
ok fair enough then makes sense