This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-23
Channels
- # announcements (5)
- # aws (8)
- # babashka (60)
- # beginners (561)
- # calva (8)
- # cider (17)
- # clj-kondo (1)
- # cljsrn (12)
- # clojure (36)
- # clojure-dev (3)
- # clojure-europe (3)
- # clojure-france (10)
- # clojure-greece (8)
- # clojure-italy (6)
- # clojure-spec (3)
- # clojure-uk (6)
- # clojurescript (30)
- # community-development (2)
- # conjure (15)
- # datascript (24)
- # figwheel-main (49)
- # fulcro (29)
- # helix (72)
- # off-topic (20)
- # pathom (7)
- # rum (7)
- # shadow-cljs (23)
- # spacemacs (6)
- # sql (8)
- # timbre (1)
- # xtdb (10)
can someone tell me what command is being run to start cider in this video at this point? https://youtu.be/9sVGy0IovH8?t=1471
Is there a guide on how making a nrepl connection in a production nodejs/java server?
Maybe this would be helpful, it's a rather concise implementation of a nrepl server made for babashka: https://github.com/babashka/babashka.nrepl @neo2551
Thanks!
I just upgraded from CIDER 22 to 25. When I cider connect to a an nREPL server (in my case a babashka nREPL server) from within a script file, it used to "just work" but now I first have to sesman-link-with-buffer. Does that sound familiar?
yeah. that was the fix for the way that things were linked in the past. they just kinda used the last repl regardless of projects. so the fix was to have things linked but this is at the detriment to non-project files
i think if you make your own elisp function to do (cider-jack-in (list :project-dir (file-name-directory (buffer-file-name)))
it should work?