Note that this is only in the default user namespace, not when you create your own namespaces :)

That makes sense! Now we're on the topic, would it make sense to have the -i flag being default, when -e is used?

Ie, the more convenience, the better?

I don't plan on adding any more bells and whistles regarding those flags, but what would be your use case?

I just went for bb for splitting some string by : in a pipe, and everything was just plain obvious, except maybe for that flag.

Honestly, it didn't take much to do bb --help, but still 😄 My casual usages of bb in pipes would be less verbose if it was just bb -e all over the place

you mean like this?

$ echo 'foo:bar' | bb '(str/split (slurp *in*) #":")'
["foo" "bar\n"]

Oh, I thought I needed the -e - and I hadn't considered (slurp *in*) - I don't need input to be a lazy seq

Better than my suggestion -thanks 🙂

Those -i -I etc flags are convenient, but I consider them mostly a left-over from early experiments when bb didn't support as much of Clojure as it does now :)

When does -e make sense? In the docs it says > -e, --eval <expr> Evaluate an expression. But that's exactly what's happening in your snippet as well?

yeah, -e is good to use, just forgot it in the last snippet I wrote. bb does work without it

but it's ambiguous when the expression is a string, then it searches for a file

you could use https://github.com/askonomm/ruuter or just dispatch on uri yourself

great also found ruuter but thought there would be more opinions about something better. But i allready liked ruuters idea reminds me a bit of hapi in the node world which i liked a lot. So nothing more fancy than that. Than i'll go that rout thank you once again @U04V15CAJ