This reminds me a bit of org-babel’s support for running blocks in any language.
I like the idea and the execution. This bit though:
makedown.sh
npm install -g ...
#!/usr/bin/env python
Gives me a bit of whiplash. I get wanting to use npm to install, since 1) lots of people have it installed and 2) it’s reasonably cross-platform and it seems like makedown is as well.
I don’t see a reason for it to be named makedown.sh instead of just makedown, though. Make itself doesn’t depend on sh to my knowledge, and you could have a makedown file with no shell build rules at all.
Comments
This reminds me a bit of org-babel’s support for running blocks in any language.
I like the idea and the execution. This bit though:
Gives me a bit of whiplash. I get wanting to use npm to install, since 1) lots of people have it installed and 2) it’s reasonably cross-platform and it seems like makedown is as well.
I don’t see a reason for it to be named makedown.sh instead of just makedown, though. Make itself doesn’t depend on sh to my knowledge, and you could have a makedown file with no shell build rules at all.
Recipes are run through sh by default, though it can be overridden to anything using the SHELL variable (including, say, python).