This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-14
Channels
- # announcements (1)
- # asami (3)
- # aws (1)
- # babashka (22)
- # beginners (39)
- # calva (21)
- # clj-kondo (10)
- # cljdoc (22)
- # cljs-dev (17)
- # clojure (93)
- # clojure-australia (3)
- # clojure-europe (39)
- # clojure-italy (3)
- # clojure-losangeles (17)
- # clojure-nl (14)
- # clojure-russia (2)
- # clojure-uk (5)
- # clojurescript (35)
- # community-development (7)
- # conjure (2)
- # cursive (13)
- # data-science (1)
- # datomic (25)
- # emacs (5)
- # events (4)
- # figwheel-main (2)
- # fulcro (12)
- # graphql (7)
- # gratitude (2)
- # inf-clojure (6)
- # leiningen (6)
- # lsp (49)
- # malli (13)
- # membrane (30)
- # minecraft (1)
- # pathom (3)
- # pedestal (26)
- # polylith (13)
- # portal (2)
- # quil (3)
- # random (1)
- # re-frame (13)
- # reagent (43)
- # reitit (6)
- # releases (1)
- # reveal (2)
- # ring (3)
- # shadow-cljs (30)
- # specter (5)
- # sql (8)
- # tools-build (1)
- # tools-deps (13)
- # videos (1)
related to the discussion just above, I wonder how are people using babashka and cider together. If you are working on multiple scripts, do you start multiple bb nrepl servers or just use the same one? And you have a different cider repl for each or you normally share that as well?
but there is no default classpath (yet). you have to set it manually like in bb.edn
:
{:paths ["."]} ;; add local dir to classpath
ah ok yeah, maybe to be on the safe side you can start a nrepl-server for each project
just a bit more tricky with the ports I guess, you have to find the next free port to use
but should not be that hard
and this will select a free port. you will have to parse that port from the output then to connect
ah nice that's cool
we could make bb write an .nrepl-port file but so far I've hesitated if we should do this since there might also be other Clojure REPLs doing that
but in #nbb that is how it works already since @viesti just decided to do this in his implementation
ah yeah, it's likely that were there is a bb script there is also a clojure project in the same project
I guess it helps the jack-in process. we could decide to not overwrite existing nrepl-port files or so. it's a tricky problem
Is there a way for babashka.curl to not automatically follow redirects? Currently --location
seems to be hard coded.
we can make this optional but right now it's not.
a PR is welcome. you can run babashka.curl from source when you require it with the :reload
keyword
a workaround would be shelling out to curl directly with babashka.process or clojure.java.shell, or use the new JDK 11 client (requires Java interop)
Thanks for the suggestions @U04V15CAJ. Will see if I can find an ideal workaround.
@U04V15CAJ Added some tests https://github.com/babashka/babashka.curl/pull/41