This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-28
Channels
- # adventofcode (2)
- # aleph (4)
- # announcements (3)
- # asami (13)
- # babashka (27)
- # beginners (74)
- # clj-kondo (18)
- # cljdoc (1)
- # cljs-dev (27)
- # cljsrn (5)
- # clojure (75)
- # clojure-australia (5)
- # clojure-europe (25)
- # clojure-uk (2)
- # conjure (1)
- # core-logic (1)
- # deps-new (1)
- # fulcro (13)
- # gratitude (8)
- # honeysql (1)
- # lsp (24)
- # missionary (45)
- # mount (2)
- # nextjournal (24)
- # off-topic (10)
- # pathom (5)
- # portal (3)
- # releases (1)
- # shadow-cljs (7)
- # specter (1)
- # tools-deps (1)
It does. I usually do:
(def windows? (str/starts-with? (System/getProperty "os.name")
"Windows"))
Is the :paths
parameter supposed in a tasks file (bb.end) supposed to work exactly the same as the --classpath
parameter?
I tried a simple example like in the docs. The namespace didn't get picked up when defined as :paths ["script"]
, but did work when I called the task using: bb --classpath script run task
I was running both command lines from the directory containing the bb.edn file and the script directory as an immediate sub-directory.
cool.. I think the problem is that I have a BABASHKA_CLASSPATH defined and it's not appending/replacing it... is that the expected behavior?
ok thanks. Another unrelated question, is there a native way to iterate, query, kill processes without resorting to ps
, kill
, etc ?
yes, you can use java.lang.ProcessHandle
for this:
https://docs.oracle.com/javase/9/docs/api/java/lang/ProcessHandle.html
That gives me an idea that you, perhaps, have already considered - creating a wrapper around clojure
that would simply make some bits of it fast. Just so that users wouldn't have to think about what to call for which task.
@U2FRKM4TW yeah, eventually some of this may be used in bb itself, but the trade-off here is binary size for example. clojure
is a wrapper around deps.clj
and deps.clj still uses a regular JVM
I'm not yet sure what the implications of this will be, but we're releasing the low level bits first and then we'll see what happens next
bb.edn
{:tasks ion-push
(clojure
{:env (let [{:keys [access-key-id secret]} ...]
{"AWS_ACCESS_KEY_ID" access-key-id
"AWS_SECRET_ACCESS_KEY" secret})}
"-A:ion-dev"
(prn-str {:op :push}))}
does this env part work like that?Windows users!
On Windows (shell "yarn")
didn't work, because on Windows you have to be explicit about the extension: (shell "yarn.cmd")
if it's not an .exe
extension. This is now improved on master.
The issue:
https://github.com/babashka/babashka/issues/1078
This is a Windows build for testing. Please give it a go. I hope I didn't break anything.
https://ci.appveyor.com/api/buildjobs/4wohqob8t5mkruvw/artifacts/babashka-0.6.6-SNAPSHOT-windows-amd64.zip