This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-01
Channels
- # announcements (2)
- # babashka (26)
- # beginners (26)
- # biff (18)
- # boulder-clojurians (2)
- # cider (16)
- # clj-kondo (34)
- # cljs-dev (4)
- # clojure (22)
- # clojure-denver (10)
- # clojure-europe (16)
- # clojure-nl (1)
- # clojure-norway (10)
- # clojure-uk (2)
- # clojurescript (25)
- # conjure (3)
- # cursive (11)
- # datomic (11)
- # dev-tooling (6)
- # emacs (6)
- # etaoin (7)
- # events (1)
- # fulcro (6)
- # humbleui (11)
- # hyperfiddle (15)
- # instaparse (2)
- # introduce-yourself (2)
- # jobs-discuss (1)
- # lsp (26)
- # malli (7)
- # reitit (5)
- # releases (1)
- # sci (6)
- # shadow-cljs (16)
- # specter (5)
- # vim (5)
There is no proxy var that follows the value of the host var, unfortunately. I've considered this but it's a bit complicated. Instead what you can do is the following: https://github.com/babashka/babashka/commit/d27efb137d54b7aa14ed4295f6e7caf272fc2aec
it depends. in the commit I linked what happens is that in the exposed "shell" function, the host dynamic var gets "just in time" bound to the value of the SCI dynamic var. So if the user does in their program (binding [...])
the host function gets to see the right value
but it can work in the other direction too. an example of that is here: https://github.com/babashka/babashka/blob/c13500cddb974ce758689ab778ddaf8047dd72e6/src/babashka/impl/pprint.clj#L132-L137