## Premise

I do not want to need to remember how to build certain projects.

I would like to self-document in code which types of build files I have encountered.

• Effortless
• Explorative
• Extensible

## Code

### zsh binding

  1 2 3 4 5 6 7 8 9 10 11 12 13 14  function zsh-cr() { trap func_trap EXIT func_trap() { tput rc } tput sc exec

### cr (bash)

• Capabilities:
• Interactively prioritise and suggest which build files to run
• Compile/run a specific build/source file, if specified
• Specify which type of file I’d like to treat this file as
• When one build file is unable to compile the project, or advance the build process, try the next one.