This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-09-17
Channels
- # announcements (47)
- # calva (10)
- # catalyst (5)
- # cider (9)
- # clj-yaml (4)
- # clojure (36)
- # clojure-europe (13)
- # clojure-norway (7)
- # clojure-uk (1)
- # cursive (1)
- # datomic (11)
- # dev-tooling (1)
- # emacs (18)
- # hyperfiddle (36)
- # inf-clojure (21)
- # polylith (3)
- # portal (3)
- # reagent (55)
- # reitit (1)
- # releases (3)
- # shadow-cljs (14)
- # solo-full-stack (1)
- # squint (6)
- # tools-build (12)
Someone on ClojureVerse looking for help with Calva: https://clojureverse.org/t/please-help-with-a-calva-error/10325
Thanks for heads-up! I think this might be the same person as reported here: https://github.com/BetterThanTomorrow/calva/issues/2314 Quite strange and opaque to me, I have very little clue about WSL. But it seems the user was happy with the “solution” to disable the WSL extension.
Weird. I work with WSL2 all the time but then I have all my projects on WSL. Looks like they have projects on Windows instead but something confuses Calva/VS Code about the project and something tries to start Docker? Maybe they had something configured wrong because that doesn't seem related to WSL to me...
Another problem here is that Calva (and the docs, I’m afraid) tricks users into thinking that Jack-in is the only way to start the REPL. So when that doesn’t work, the user is “stuck” and hindered from doing whatever it is they set out to do. I’m not ready to backtrack on the recommendation to prefer Jack-in for users new to Calva, just yet, it has really helped with avoiding the new-user-support to be all about nrepl dependencies, and such, like it used to be before jack-in. But there should be a way to communicate that it is a recommendation, not a requirement…
Now that the connect/jack-in sequences can be completely customized and "automated" on a project-by-project basis, I have switched to jack-in for all my projects so I'm with you on recommending it to beginners...
Haha, yeah, we have nudged it, inch by inch, to get pretty useful beyond just making sure the dependencies are met. I find myself using it more often than not too. I still like how starting it myself (even if using the jack-in command line provided by Calva) survives a reload of the VS Code window, but often I can’t be bothered and just use jack in.
Yeah, the REPL surviving a VS Code reload is very helpful:grin:
I notice that when I connect the repl on a (virtual) Windows box I have access to it also connects to a kubernetes/docker URL. The WSL extension is installed, which must be some default, because I can’t recall installing it. I’ve only installed Calva on this machine’s VS Code. A difference from the user reporting the issue in OP is that the connection succeeds.
Another Windows user reports repl connection doesn’t work. This time no WSL extension involved. https://github.com/BetterThanTomorrow/calva/issues/2316
Another Windows user reports repl connection doesn’t work. This time no WSL extension involved. https://github.com/BetterThanTomorrow/calva/issues/2316