Add capability to do "do nothing" scripting. Incremental Automation

[mofosyne]

https://blog.danslimmon.com/2019/07/15/do-nothing-scripting-the-key-to-gradual-automation/

Not sure how the syntax would work. But the idea is you would have a just command that has multiple steps... where you press 'y' to move to the next step. Then you can add automation steps in between as you figure things out...

Maybe?

// Test Runnable Documentation
just_run_doc:step-1:
    "Say hello world first"
    echo hello world

just_run_doc:step-2:
    "pet the dog"

just_run_doc:step-3:
     "reboot the computer"
     reboot -f

// Test Runnable Documentation
just_run_doc:
 - step-1: Say hello world first
    echo hello world
 - step-2: Pet the dog
 - step-3: Reboot the computer
     reboot -f

// Test Runnable Documentation
just_run_doc:
:: Say hello world first
    echo hello world
:: Pet the dog
:: Reboot the computer
     reboot -f

[casey]

You can do this with read::

foo:
  @read -p 'reboot computer'

However, putting that in front of every line would be pretty annoying. I can potentially see the value in a setting, or maybe a command line flag, which steps through every command and waits for user confirmation before running recipes lines. But I'm not sure how much use it would get, so I'd want to see multiple users requesting it.

[laniakea64]

the idea is you would have a just command that has multiple steps... where you press 'y' to move to the next step.

You can use [confirm(...)] attribute and along the lines of your first example:

# Test Runnable Documentation
just_run_doc: _just_run_doc1 _just_run_doc2 _just_run_doc3

[confirm("Say hello world first")]
_just_run_doc1:
    echo hello world

[confirm("pet the dog")]
_just_run_doc2:

[confirm("reboot the computer")]
_just_run_doc3:
     echo reboot -f