specify shell on the fly doesn't work. about just

[thisismygitrepo]

it worked, I just had to push recipe to come after the optional arguments. But still, it should work either way.

[runeimp]

It would be next to impossible to allow both ways. What if a recipe that is called can accept options that have meaning to Just? If you allowed both how would you specify that the option that was written after a recipe was actually for Just and not the recipe?

[thisismygitrepo]

You're right, that would be confusing. I think it customarily handled with -- to indicate that whatever comes next is arguments for the command called.

[runeimp]

Yes, but many (most ?) people forget about --. It is also a UNIX standard to put all options for a command after the command and before all other arguments. Depending on the command there is no possible consequence to putting options anywhere on the command line. But that is only true for a relatively small subset of all common commands on a system. Allowing this but requiring -- to avoid issues is error prone and can fail without explanation depending on the contents of the target recipe or possibly sup recipe calls. Where as it stands currently it just fails immediately and is easy to recognize and recover from.