In bb this isn't necessary and this namespace isn't exposed in bb

ah so the Clojure.pprint bit only applies when invoking clj. That makes sense in hindsight 🙂

thanks

yeah, and I think nowadays it isn't mostly necessary at all to call it yourself anymore, since it's automatically done when clojure.pprint is already loaded

Not exactly a follow up, but debugging the same thing (and my clojure is 5+ years rusty, so I’m probably misreading)… I want to pass both opts, and a command sequence to process. The third/fourth rows here suggests that I can’t have both:

(parse-args ["git" "ls-files"]) ; {:prev nil, :cmd ["git" "ls-files"], :opts nil}
(parse-args [["git" "ls-files"]]) ; {:prev nil, :cmd ["git" "ls-files"], :opts nil}
(parse-args [{} ["git" "ls-files"]]) ; {:prev nil, :cmd ["[git" "ls-files]"], :opts {}}
(parse-args [{:cmd ["git" "ls-files"]}]) ; {:prev nil, :cmd [], :opts {:cmd ["git" "ls-files"]}}

(parse-args [{} "git" "ls-files"])

so you can do:

(apply process opts "git" remaining-args)

(parse-args [{} "git" "ls-files"]) ; {:prev nil, :cmd ["git" "ls-files"], :opts {}} does work, thanks! It feels a bit incongruous that it flattens in the “first position” sequence, but not the second. I’m curious, is there a reason to avoid that case? (Not seeking controversy, but curious since the behavior is counter to my intuitions after my initial sequence experiment worked.)

The process library moved from the syntax (process [args] ?opts)) to (process ?opts ...args) since this was easier in combination with apply. parse-args bridges that migration

That this is the case shouldn't matter to you as a new user, the README reflects how you should currently use the library

I have considered allowing this:

(process ?opts ...preceding-args [remaining-arguments])

but this would create another migration which could lead to confusion

right now you have to do it like this:

(apply process ?opts ...preceding-args [remaining-arguments])

I hope all is clear now?

Close, but not quite — the “considered allowing” form seems that would imply full something like:

;; both args and extra-args arguments are flattened into command
(process ?opts args & extra-args)

Perhaps I misunderstand some of the nuance in the type checks due to the argument reordering. My mental model assumes 3 basic types: map (opts), seq (array of args), or string (arg).

The supported syntax is:

(process ?opts ...strings)

(process ?opts [...strings]) was never supported - if it works, it's purely accidental

Just go by the docs and not by what accidentally works

lol, I thought the repl was the doc 🙂

there are many things in clojure that work, but not according to prescribed usage. E.g. (inc (merge 1))

thanks for the guidance 🙂

Cool! But see in 🧵

deps-try                                                                                               127 ✘  14:03:38
----- Error --------------------------------------------------------------------
Type:     clojure.lang.ArityException
Message:  Wrong number of args (3) passed to: babashka.deps/clojure
Location: /Users/dmg46664/.gitlibs/libs/io.github.eval/deps-try/dca3e52fa7e723021ae4f8c62d3c111771d27bde/src/eval/deps_try.clj:26:40

----- Context ------------------------------------------------------------------
22:   (str/trim (with-out-str (deps/clojure {:dir (str tmp)} "-Spath" "-Sdeps" (str {:deps deps})))))
23:
24: (defn -main [& args]
25:   (fs/with-temp-dir [tmp {}]
26:     (let [verbose-output (with-out-str (deps/clojure {:dir (str tmp)} "-Sverbose" "-Spath"))
                                           ^--- Wrong number of args (3) passed to: babashka.deps/clojure
27:           cp-file (parse-cp-file verbose-output)
28:           basis-file (str/replace cp-file #".cp$" ".basis")
29:           requested-deps (try-deps/parse-dep-args args)
30:           default-cp (deps->cp tmp '{org.clojure/clojure {:mvn/version "RELEASE"}})
31:           requested-cp (deps->cp tmp requested-deps)

----- Stack trace --------------------------------------------------------------
eval.deps-try      - /Users/dmg46664/.gitlibs/libs/io.github.eval/deps-try/dca3e52fa7e723021ae4f8c62d3c111771d27bde/src/eval/deps_try.clj:26:40
clojure.core/apply - <built-in>
user               - <expr>:1:38

@U03B2SRNYTY Upgrade your bb

Works! Thanks.

@UHZPYLPU1 Yes:

(shell {:extra-env {"MY_ENV_VAR" "1"} "clojure -M:foo:baz")

or even better:

(clojure {:extra-env {"MY_ENV_VAR" "1"} "-M:foo:baz")

@U04V15CAJ you rocks! Thanks!

@U051V5LLP locales aren't automatically included in a native image since they take up a lot of space. I think only English is included

aha - good to know, thanks for clarifying!

and because these are defined in java you'd need a custom image to add more, is that correct?

yes. we can enable some of those but it's hard to say which ones we should enable, other than english

cool, no worries, just making sure there wasn't a way to load them dynamically. Thanks!