There is no way to do this with jack-in currently. You will have to use connect.

Please file an issue about it.

<!subteam^S03BGSAUPTQ|@calva-team> since we are building a command line as an array which we then execute. Maybe a way to solve this more general case is to make the command line array itself configurable? That would then be used instead of Calva building it. We could have some place-holder variables for the dependencies. So in the case above, the user would use a custom connect sequence with something like so in it:

"jack-in-command-line": ["npx", "shadow-cljs", "-d", "$CIDER-NREPL-VERSION", "watch", ":app", "some-arg-1", "some-arg-2"]

"jack-in-command-line": ["start-my-repl.sh", "$CIDER-NREPL-VERSION"]

"jack-in-command-line": ["start-my-repl.sh"]

maybe prefix the env vars with CALVA_

but otherwise that sounds good to me

I like escape hatches like that that give you total control

Yes, those vars should be properly prefixed of course. $CIDER-NREPL-VERSION above is not an env var, just to clarify.

oh absolutely, but even in that case prefixes prevent possible overlap, like namespacing keys

I really like this idea. it was forever a pain in emacs that it wasn't simple to override these things

Not sure I follow, please elaborate some.

To have developers as the end users does provide room for some solutions that would be a bit crazy otherwise. 😃

I like the idea as well

I mean with the variables we'll interpolate into their command array it still pays to prefix with CALVA since it's possible that any other value could be a legitimate value they don't want interpolated

I assumed we couldn't get variables in the array interpolated by the shell. You think we can? Then we don't need to interpolate at all. Just execute with env vars and the user can use them either in the array or inside some script.

no, I meant outside the shell

No harm in namespacing i feel like