This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-18
Channels
- # announcements (12)
- # babashka (6)
- # beginners (62)
- # calva (3)
- # cider (41)
- # clerk (5)
- # clojure (192)
- # clojure-bay-area (1)
- # clojure-europe (14)
- # clojure-norway (97)
- # clojure-uk (6)
- # clojuredesign-podcast (4)
- # clojurescript (30)
- # code-reviews (7)
- # cursive (32)
- # datahike (4)
- # datomic (35)
- # docker (8)
- # emacs (8)
- # events (1)
- # fulcro (13)
- # helix (19)
- # hoplon (4)
- # hyperfiddle (33)
- # jobs-discuss (10)
- # membrane (11)
- # missionary (19)
- # off-topic (28)
- # polylith (8)
- # portal (10)
- # practicalli (8)
- # re-frame (31)
- # reitit (6)
- # shadow-cljs (39)
- # timbre (3)
- # vim (1)
- # xtdb (6)
Hello. One simple question. How do you tell when a Babashka script is executed from the terminal (via #!/usr/bin/env bb) in contrast to loading the file into a nREPL session? I'd like to test and play around with the helper functions but don't want to run the main script form.
this section: <https://book.babashka.org/#main_file> might be what you're looking for
with what black magic does the self-contained binary / uberjar work? So you stuff together the binary and the uberjar into a binary and java.util.zip.ZipFile just skips that binary and looks for the the zip?
aha, TIL https://en.wikipedia.org/wiki/ZIP_(file_format) > ZIP archives can also include extra data that is not related to the ZIP archive. This allows for a ZIP archive to be made into a self-extracting archive (application that decompresses its contained data), by prepending the program code to a ZIP archive and marking the file as executable.