How are you using it? It should be used as a global option, ie one of the first things you pass

I tried with a shabang on my script, like so:

#!/usr/bin/env -S bb --prn -cp ./bin

Message:  File does not exist: --prn

Ah shame, I guess it’s not compatible then

Why not use explicit printing?

My script blows up in 171 (for reasons I am investigating) and it is completely silent. With --prn the error and stack trace is printed.

That sounds like a try/catch which then returns the exception as a value which then gets printed

Hmmm, it blows up silently with or without --prn , (it's a shell-out). I added an explicit throw when I get non-zero exit value. Maybe that gets returned...

If you use ‘process/shell’ it should throw

I'm using java/shell. It's an old script. Has been ticking along since very long and suddenly stopped doing anything some week ago.

I can rewrite using process/shell. But I want to understand what changed.

—prn does nothing else than print the last value like the old version did. It has no impact on error reporting. If you use an explicit ‘prn’ on the last value then behaviour should be 100% the same in both versions

Thanks. I'll do that for now.

wow, I didn't know about the env -S trick - is that to support multiple args?

That isn’t a cross platform feature

I guess env -S works on macOS and Linux, isn't that cross-platform enough?

I remember something being not cross-platform about it, but I'd have to look it up

but I guess if nobody complains and it works, keep using it :)

It seems it started working on linux a few years ago, but it wasn't cross platform before. https://unix.stackexchange.com/a/477651/28294

Looks like an auth issue

it is a private repo, I am running it locally so would have expected it to use my auth.

I can pull and push to the repo, or is it a case of you can only use public repos

Well that's what the error means, without any idea of what you're doing code-wise we can't offer any more help 🙂

{:paths ["bb"]
 :deps {io.github.organisation/build-tools {:git/sha "mysha"}}
 :tasks
 {}} 

Try :deps {name/build-tools {:git/url "url" :sha "mysha"}}

cheers, that does indeed seem to work, which makes me wonder what the differece is

The difference is that's not how you define a git dep 😉 Probably couldn't infer the repo from the name

lol, I got that from https://clojure.org/guides/deps_and_cli#_using_git_libraries 🙂

Yeah, io.github.* should work :thinking_face:

which does not use :git/url

Maybe babashka doesn't support it?

Yeah that's a clojure guide

perhaps one uses https as i used the git link in the url,

fair enough I did look in the babashka book for an example, it works now so thanks for the assistance 🙂

babashka supports everything deps.edn :deps supports

in doubt, try to fetch the dep with deps.edn - it should work totally the same

Maybe install the script in the system with https://github.com/babashka/bbin and allow the script to use current folder (by default) and have a -f option to pass an optional folder?

Yes, #C0400TZENE7

Or make a bash wrapper which sets:

bb --config "$(dirname "${BASH_SOURCE[0]}")/../bb.edn" -m magic.main "[email protected]"

I am considering setting the --config flag automatically when you execute a script outside of the current directory, so it picks up on the bb.edn of the script, but I'm not sure if this will break any existing setups. Also this would only work for *nix, not on Windows, and bb aims to be a cross-platform tool. So in the end, bbin is the preferred solution.

Alternatively use https://direnv.net/. Create $PROJECT_ROOT/.envrc with

PATH_add bin
export PROJECT_ROOT=$(expand_path .)

(this is indeed limited to working from the project, else bbin FTW)

For my latest scripts, I’ve copied the folder structure from https://github.com/borkdude/carve. 1. All dependencies are in deps.edn 2. bb.edn refers to deps.edn dependencies 3. bb.edn also gives a bbin directive for what I want the binary to be called. For local installation, I install with bbin install . or bbin install . --as myscript-dev if I want both a local binary and a proper install. Local installs automatically pick up any changes to your script, so it’s very easy make a change, run it again, etc; you don’t need to re-run bbin install. The “carve structure” also makes it possible to REPL into your project with both babashka and clojure.

what about adding /path/to/src/ to bb classpath? This way you dont need to change the cwd to call bb -m magic.main?

but all deps in path/to/project should also be added, which is what --config is for

Thanks for all the suggestions. --config does exactly what I was looking for

Ya think james will go for a bb compatible badge?

Worth a shot ;)

https://github.com/weavejester/cljfmt/pull/295

Nope! Oh well.

not sure what I am doing wrong:

$ bbin --version
bbin 0.1.8
$ bbin install 
{:coords
 #:bbin{:url
        ""}}
$ cljfmt --help
zsh: command not found: cljfmt

@U051GFP2V Do you have a fully functioning bbin installation?

i.e. did you add the .bbin dir to your PATH?

See 2. here: https://github.com/babashka/bbin#installation

Oh yeah, I’ll read the manual next time 🙈

added the path and It works now

Here is a blog about that: https://blog.michielborkent.nl/speeding-up-builds-fs-modified-since.html