Unordered named recipe argument flags about just

[runeimp]

It's hard to understand what you are trying to solve exactly. There is nothing stopping you from passing options that get used by the internal recipe code. But recipes are not automatically functions or scripts. Just is a task runner intended to replace make in situations where it is used as a task runner instead of a code builder. So any input for a recipe is expected to be handled by the tasks, code, etc. within the recipe itself.

If you code a recipe as a shebang script, your script should handle the recipe input as needed, or the various tasks should be passed whatever input is appropriate based on how you designed the signature of the recipe. I believe there are some tools out there that may do what you're expecting as a specific feature of the tool. But just is not one of them. And I believe this was discussed much earlier in the projects life cycle. It is also used a lot on many projects, often by automated systems as well. The changes you're asking for would likely break a large portion of them out-of-the-gate if implemented.

@casey do you have any thoughts? I have a feeling I'm overlooking something regarding all of this.

@Jarthianur I have a feeling I'm being harsh in my response. If that is the case please forgive me. I'm not feeling quite right today but wanted to give you some feedback on your request.

[casey]

I don't think this is a terrible idea, but there's actually an issue open for this, #476, so closing as a duplicate. Check out #476.

This would be a backwards incompatible change, since it's possible to pass flags as a recipe argument:

foo arg:
  echo {{arg}}

$ just foo --bar
echo --bar
--bar

The version proposed in #476 requires declaring that arguments will be accepted as a flag, so as to be backwards compatible:

foo --arg: