--save flag for exec-stdin and exec-file that record code and timestamp.

[lpil]

Proposal

Given a live coding performance where the user is using echo $CODE | sonic-pi-tool eval-stdin --save some/dir

at the end of the performance the given directory would contain one file for each time code was evaled, with timestamps, so the performance can be replayed.

some/dir
├── sonic-pi-code-20170101170456.rb
├── sonic-pi-code-20170101170503.rb
└── ... etc ...

This could then be used with a replay command to be implemented later.

Discussion

• Is --save a good name?
• Is the code in a file and timestamp in the filename enough info? Or should we save a JSON blob so that more data can be stored?

[iamjonny]

Is this working yet? Great idea, I'd had a similar one with the git autosave commit log but don't have the skills yet to make it work, or test to see if already accurate (or any delays introduced during replay of committed runs at commit_timestamps

👍👍👍👍👍

[lpil]

Nobody is working this as far as I'm aware.