Run other recipe?

[fgblomqvist]

If I have a file like:

foo:
  echo foo

bar:
  echo bar
  foo

It will error because there is no such command as foo. Makes sense. But how can I call a recipe from another? I don't want to have to use just foo since working directory etc. isn't guaranteed.

[casey]

It isn't very pretty, but you can do:

foo:
  echo foo

bar:
  echo bar
  just --justfile {{justfile()}} foo

(-f can also be used instead of --justfile.)

This has come up a few times before, so ideally there would be a nice way to do this without such hackery.

[casey]

That would miss command line flags as well, so maybe it's not a great approach.

[casey]

It's weird, but a prefix could work:

bar:

foo:
  echo a
: bar
  echo b

[fgblomqvist]

Yeah I was gonna ask how the @ symbol works? Because if I write @echo "Hello" just decides not to print the command, which is not a valid bash syntax. So yeah sounds like coming up with some other line prefix should work?

[casey]

@ and - are sort of odd ducks. I added them because make supports them, but I'm not totally sure that it's a good idea to more.

I was thinking of a prefix that would go before the indentation, not after it.

[fgblomqvist]

I lean more and more towards just using just as the argument parser and then storing most/all code in bash scripts. That way, you don't lose out on just lacking file inclusion support, and you don't have to worry about this feature either (being able to run other recipes). It's not 100% as elegant as just doing everything, but without file-inclusion support there's not much to do anyway. But yeah, perhaps it would still make sense to add this feature 🤷