os.args() and passthru from CLI

[edhemphill]

i'll try to update this PR with some tests.

[myzie]

This is looking good. Just left a couple minor questions/comments.

[edhemphill]

updated. see what you think

[myzie]

@edhemphill - this all looks good. Just this one little update to do:
https://github.com/risor-io/risor/pull/102/files#r1321470932

After that I think this is good to go. I'll give it a try just to sanity check.

[edhemphill]

good catch

[myzie]

This looks good to me.

go run ./cmd/risor -c "os.args()" -- -foo --bar baz
[
  "-foo",
  "--bar",
  "baz"
]

One thing we should look at as a follow-up is what the shebang line should be now. What I had in there before doesn't seem to work, but I don't think that needs to hold up this PR.

Not working:

#!/usr/bin/env risor --

os.args()

[edhemphill]

yeah - i see what you're saying... will try to fix. It's not executing the script.

[edhemphill]

so in my testing this works:

test.tm:

#!/usr/bin/env /home/ed/work/risor/cmd/risor/risor 

os.args()

As well as some other variations with and without env. The issue is the script arg of the file with the #! is added after the -- so it gets passed to the risor script.

With the above, you can pass args to the risor script like:

 ./test.tm -- 1 2 3 

[
  "1",
  "2",
  "3"
]

To get around having to pass args behind a -- you could have a wrapper script for risor. As an example:

risor.sh:

#!/bin/bash

exec /path/to/risor "${1}" -- "${@:2}"

test.tm:

#!/path/to/risor.sh

os.args()

$ ./test.tm 1 2 3 

[
  "1",
  "2",
  "3"
]