This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-12
Channels
- # adventofcode (67)
- # announcements (8)
- # babashka (46)
- # beginners (154)
- # calva (5)
- # cider (9)
- # clara (5)
- # clj-kondo (34)
- # cljdoc (31)
- # cljsrn (4)
- # clojure (146)
- # clojure-europe (5)
- # clojure-italy (3)
- # clojure-losangeles (2)
- # clojure-nl (149)
- # clojure-spec (22)
- # clojure-uk (73)
- # clojured (6)
- # clojurescript (95)
- # clojureverse-ops (3)
- # cryogen (7)
- # cursive (12)
- # data-science (1)
- # datomic (9)
- # docker (1)
- # emacs (1)
- # figwheel-main (1)
- # hyperfiddle (1)
- # jobs (3)
- # malli (29)
- # nrepl (2)
- # off-topic (61)
- # pathom (6)
- # pedestal (1)
- # planck (1)
- # reitit (19)
- # shadow-cljs (52)
- # spacemacs (5)
- # tools-deps (24)
- # vim (30)
- # yada (6)
Preliminary classpath docs: https://github.com/borkdude/babashka/tree/classpath#classpath Feedback welcome.
Mac binary: https://2278-201467090-gh.circle-artifacts.com/0/release/babashka-0.0.41-SNAPSHOT-macos-amd64.zip Linux binary: https://2282-201467090-gh.circle-artifacts.com/0/release/babashka-0.0.41-SNAPSHOT-linux-amd64.zip
One thing I'm wondering about: should src
be the default classpath if the --classpath
option is omitted? or the current working directory? Both? Neither?
at least for clojure, i think the current working directory (project dir?) is typically not on the classpath. does that seem right?
lgtm:
$ ./bb --classpath ./examples "(require '[classpath])"
hello from classpath
$ cat examples/classpath.bb
(ns classpath)
(println "hello from classpath")
you can also try src-bash/bbk -Sdeps '{:paths ["examples"]}' -e "(require '[classpath])"
$ ./src-bash/bbk -Sdeps '{:paths ["examples"]}' -e "(require '[classpath])"
hello from classpath
I guess you can revert to using bb --classpath $(clojure -Spath)
worst case, best case it will be ported to babashka 😉
at least, I didn't see installation instructions for it. I guess theoretically it could
it's funny you tried the .bb extension, I didn't document that explicitly but bb will first look for a .bb file, then .clj, then .cljc
so you can make a tools.cli entrance script with fast startup, before firing up the JVM and fail fast, all within the same code base using the same deps.edn
that sounds vaguely like something planck or some other thing mfikes did at some point
what planck does is show the prompt and accept input before it's even ready, so by the time you finish typing, the runtime is ready. it just seems faster
ah, right (having the .bb file extension should make things easier for tooling -- this is a bit of a headache trying to tell apart jvm clojure from clr clojure)
re: planck and windows: https://github.com/planck-repl/planck/issues/416 -- looks like not yet?
re: bb on windows, it would be helpful if the issue about it collected the current state in the top post / first comment, so we can keep track of the state of affairs