| Yes I agree with this. I use shell instead of make, because make wrapps shell and its syntax collides very poorly with it. For example, the PID is now $$$$ and not $$. Most people forget to mark their targets .PHONY, so they have a subtle bug in their build (touch build; touch test). ---- But shell also suffers from the problem where it doesn't list the commands. I filed a bug for Oil shell here: https://github.com/oilshell/oil/issues/751 I mentioned a couple other "frameworks" there like just, go, Taskfile, etc. But it should really just be built into the shell, since it's so common. And there should be command completion too, which I think bash-completion has for Makefiles on many distros. Apparently there is no standard name for this kind of "task runner". But I think shell makes a lot more sense than a custom format, because there are many instances where you need a simple loop or conditional. It scales better. (And Oil also fixes bad shell syntax while remaining compatible: http://www.oilshell.org/blog/2020/01/simplest-explanation.ht...) If anyone wants to help let me know :) The code is plain Python and pretty hackable. However it generates fast C++, so you get the best of both worlds (in progress) |