| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | more protection against data loss | Kartik K. Agaram | 2021-12-17 | 1 | -1/+11 |
| | | |||||
| * | . | Kartik K. Agaram | 2021-12-17 | 1 | -13/+0 |
| | | |||||
| * | . | Kartik K. Agaram | 2021-12-11 | 1 | -0/+2 |
| | | |||||
| * | handle non-existent file | Kartik K. Agaram | 2021-12-11 | 1 | -1/+5 |
| | | |||||
| * | snapshot: migrate all sample apps to new format | Kartik K. Agaram | 2021-12-11 | 1 | -1/+3 |
| | | |||||
| * | snapshot: writing working? | Kartik K. Agaram | 2021-12-11 | 1 | -5/+99 |
| | | | | | | | This is a complete mess. I want to abstract reading multiline strings behind a function, but the lookahead requirements for that are quite stringent. What's a reasonable abstraction here? | ||||
| * | snapshot: key/value lines after multiline strings | Kartik K. Agaram | 2021-12-11 | 1 | -29/+43 |
| | | |||||
| * | snapshot: start reading a new format | Kartik K. Agaram | 2021-12-11 | 1 | -0/+73 |
| I really wanted to avoid getting into defining or parsing new file formats. However, using the entire power of Lua is not ideal, as described earlier in Konrad Hinsen's bug. In addition to everything else, it's a vector for arbitrary code execution when someone loads an untrusted image. I could use JSON, but it requires ugly string escaping. Seems cleaner to just use YAML. But YAML is complex and needs its own dependencies. If I'm going to do my own, might as well make the multi-line string format really clear. I can't yet write the new format. | |||||