I guess I can use *command-line-args* directly?

-x expects key-value pairs, like -X in Clojure

Looks like *command-line-args* contains the remaining args, so I'll use that. Unless that's unsafe?

no sorry I was wrong, positional args work, like this:

(ns dude)

(defn foo
  {:org.babashka/cli {:coerce {:a []}}}
  [{:keys [a b c]}]
  (prn [a b c]))

$ bb -cp /tmp -x dude/foo -a 1 2 3 -b 1 -c 2
[[1 2 3] 1 2]

or do you mean, remaining arguments?

oh I meant that I want to pass in a bunch of files names, like a.txt b.txt c.txt

(ns dude)

(defn foo
  {:org.babashka/cli {:coerce {:a []}}}
  [{:keys [a b c] :as m}]
  (prn (meta m))
  (prn [a b c]))

$ bb -cp /tmp -x dude/foo -a 1 2 3 -b 1 -c 2 1 2 3
#:org.babashka{:cli {:args ["1" "2" "3"]}}
[[1 2 3] 1 2]

yeah, you can get this via the metadata of the passed map

oh the metadata 🤯

cool cool cool thanks! 🙂

* is a bash-ism. process does not launch bash, it only launches programs

if you want to list files from a directory, you can use fs/list-dir

I see. I was trying to do a tar cvzf something.tgz /tmp/something* when I hit the issue. I'll work around it, Thanks for the clarification.

you can shell out to bash if you want. (shell "bash -c '...'")

the fs api is great, I think I'll lean in to it to solve this one. Much appreciated.

It's probably best to minimize the amount of code in bb.edn and just require an external file and do the coding in there

How do you want Calva to be aware? (Calva maintainer here.)

I really only have the calls to the entry points for each task, but it would be good to a have help when creating the function calls and also show that a function is used.

@U0ETXRFEW what I notice is that the functions that are used as the entry points show as unused, in someways helpful as you can find them, but in otherways it also keeps making me think I have made an error somewhere.

this is probably a clojure-lsp issue

can you navigate to the function from bb.edn?

I don’t know what’s possible here. This is functionality that Calva sources from #CPABC1H61 and. by proxy, #CHY97NXE2. @U04V15CAJ knows more about what’s involved. 😃

It is a bit of a strange request as you are in effect tying an .edn file as if it were a code file, which is unusual for tools to pick up on.

No you can't navigate from bb.edn file.

@U4C3ZU6KX navigation from edn files to functions does work when the symbol is fully qualified

e.g. foo.bar/baz should work

clj-kondo could try to support code in bb.edn a bit more

feel free to post an issue about it

with some examples. let's take a tiny step to begin with

I am not seeing that. I have :

:tasks   {:requires ([convert.core :as  core]
                      [convert.utils :as utils]
                      [clojure.tools.cli :as cli])
          convert (do
                          (println "Converting " (:import-dir options))
                          (core/handle-conversion (:import-dir options)  (:export-dir options)))}

And the core/handle-conversion shows No Definition when I use Go to Definition.

try convert.core/handle-conversion

Thanks that worked. That just leaves the showing as unused in the convert.core.clj file.

ok, the latter can be solved in #CPABC1H61

but perhaps clj-kondo could try to better support bb.edn file by transforming the code and then linting that

issue welcome

Where do I raise it?

clj-kondo

OK will do.