Fork me on GitHub
#cider
<
2017-02-26
>
bozhidar07:02:53

@hans that's quite curious, you might want to file a ticket about it

bozhidar08:02:15

seems to me we could have made the problem easier to spot if the message included some details about the connection endpoint

pesterhazy13:02:23

@bozhidar or just use 127.0.0.1?

hans15:02:50

@pesterhazy that'll break systems which don't have ipv4

pesterhazy15:02:07

is that a practical possibility?

pesterhazy15:02:21

I've never heard of such a desktop system

hans15:02:08

i'm not using any linux desktop systems at all, and i've seen servers without ipv4 in the real world.

hans15:02:33

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.

pesterhazy15:02:27

the proper solution seems for the nREPL server to listen to ::1 as well as 127.0.0.1

hans15:02:31

i agree. it should try to listen to both, if supported by the system

pesterhazy15:02:11

also cider could use localhost but prefer ipv4 if available

andrea.crotti15:02:55

when I do do a cider-jack-in-clojurescript and I have two repls

andrea.crotti15:02:12

with C-c C-z I always switch to the clojurescript one

andrea.crotti15:02:19

no way to switch to the clojure repl?

andrea.crotti15:02:29

I mean I can just switch buffer of course

richiardiandrea16:02:18

@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.

andrea.crotti16:02:52

ah yes you're right actually @richiardiandrea

andrea.crotti16:02:02

ok fair enough then makes sense