I've done some experiments with lanterna: https://twitter.com/borkdude/status/1569351199404576770 It worked pretty well, but I don't consider the pod stable. You can play around with it locally though and see how far you get. But if you want some simple dialogs, then this may be a nice approach: https://www.pixelated-noise.com/blog/2022/12/09/dialog-and-babashka/index.html Node.js / #nbb might give you better options using something like reagent and Ink: https://github.com/babashka/nbb#reagent

you can obtain (exerimental) binaries for pod-babashka-lanterna here from the builds: https://app.circleci.com/pipelines/github/babashka/pod-babashka-lanterna and then play around with it - docs are here: https://github.com/babashka/pod-babashka-lanterna

This could work too https://www.pixelated-noise.com/blog/2022/12/09/dialog-and-babashka/index.html

@U883WCP5Z https://clojurians.slack.com/archives/CLX41ASCS/p1674094619717169

@U04V15CAJ thanks for sharing!

This can take so many directions: • Should accessing static functions on a namespace such System/exit trigger the reflection warning? • Does kondo have different linters for babashka files? • Should babashka files have a .clj extension? (Our babashka file uses clj-kondo as a pod so it's definitely bb only)

This is an optional linter. You can set warn-on-reflection in babashka, but it has no effect. You can use the .bb extension as well if you want

or you can disable the linter for babashka scripts using an additional config

We have it on inside our .clj-kondo/config.edn , since we do care about it in production.

Hm, how would we define an additional config only for babashka scripts? So e.g. src and test get linted with one config, then bin gets linted with something else?

In babashka you can also use (throw (ex-info "msg" {:babashka/exit 1})

I'd say, just go with the *warn-on-reflection* in your bb script, even though it has no effect, it's at least consistent with the rest of your code

that does make sense

Thanks for the input!

Use babashka.process/process , not shell

Sorry, I sent that before I meant to, I've edited to include more information. I'm using the process library

e.g. this works for me:

bb -e '(babashka.process/process {:inherit true} "/tmp/sleep.sh")'

Hmm. I have this task with exactly those bash scripts above, and it's not doing anything

bg        (ps/process "./scripts/test2.sh &" {:inherit true})

Oh, removing the & from the string there does nothing either, I just added that to try it

you should put {:inherit true} before the string

Oh, whoops 😅 Still nothing though...

$ cat /tmp/sleep.sh
# test.sh
sleep 5
echo "HERE"
$ bb -e '(babashka.process/process {:inherit true} "/tmp/sleep.sh") nil'
$ HERE

Then tell me if that works or not for you

Hmm, that still doesn't work.

$ ./scripts/test2.sh

$ HERE

$ bb -e '(babashka.process/process {:inherit true} "./scripts/test2.sh") nil'

$
$

what OS are you on?

"bash -c './scripts/test2.sh'"

Mac

Wrapping it in bash -c doesn't work either 😅 Oh well, it's not a big deal.

Weird, I'm also on mac

@U01BH40EA0Z Perhaps you can make a github repo so we are executing 100% the same code - I find it weird that we're both on a mac and we get different behavior. What's your bb version?

Are you on the latest babashka?

The opts-first syntax will silently fail on older versions

yeah, so let's make a repro so we're 100% sure about the code and also specify the bb version

@U04V15CAJ Here's a repo. I'm using babashka version v1.0.168 and MacOS 13.0.1

Where's the repo? 1.0.168 should be good

Oh lol, sorry, forgot to paste the link https://github.com/nixin72/testing

@U01BH40EA0Z This works perfectly over here:

$ bb tasks
The following tasks are available:

test
borkdude@m1 /tmp/testing (main) $ bb test
borkdude@m1 /tmp/testing (main) $ HERE

Huh... I'm even also using zsh

Can you do file $(which bb) and paste the output?

Can you test from a vanilla bash shell?

$ bash

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit .
bash-3.2$ bb test
bash-3.2$ HERE

Ooh I have bb aliased to rlwrap bb, that might have something to do with it

Yup, running in bash where the alias doesn't exist works

yep, I can repro that ;)

:face_palm:

mystery solved then

Thank you so much as always @U04V15CAJ! I really appreciate it

Glad we solved it