There's not supposed to be anything sexy about terminal apps, stop trying to dress them up.
To be honest, the main use of the script was helping engineers use tmux even if they had never had to before (y'know, mouse clicky, familiar window management keyboard shortcuts etc, automating the process of requesting access to a tmux session, receiving those notifications, and granting access). But I definitely improved a number of runbooks or found the "aha, that's how we broke it!" by watching those replays, in particular the timing of events in different terminal sessions.
An extremely useful feature in scriptreplay is the "remove all the long pauses" option.
Animated tutorial-like ‶videos″ of CLI that are much smaller than gifs/mp4s.
I can't share them because they're not openn-source, but I made quite a few of those for consumption by other teams within my company, and they were always very much appreciated.
You may find it silly, but the wow effect is very efficient to onboard people.
> # See how easy it is to record a termina
(I missed the l at the end because I copied this on my phone with the bad handlebars for selection, but I'm preserving the mistake for authenticity.)
If you're a verbal learner (reader), that's fine. This additional method covers the visual learners, while the auditory and kinesthetic learners we circle back on with smaller workshops.
Sometimes it's nice to be able to go back and see recordings of boot logs, where timing is useful, and navigating bios screens or other similar user interfaces.
If it needs documenting it's nice to record it as you're doing it, and writing the documentation as you're rewatching the recording so you can copy paste the important moments.
It's not so nice to rely on only a recording as documentation.
There's probably a better way to do this, but I don't know what it is.
It produces a file containing just what got sent to the terminal, no timing information. -T lets it output timing info but as a separate file.
(Also in this vein, the ttyrec format is a binary format that interleaves timing and terminal output. It’s very similar in function to the asciicast v2 format, but much more compact by dint of being binary rather than JSON, and asciicast v2 has a few extra features like being able to declare the duration in the header, record environment variables, record the colour palette, and add markers. I wish asciinema had built on the ttyrec format at least for its canonical format (like WASM has the binary and text formats), and asciicast v1 was bad in a few ways, but from asciicast v2 it’s much more reasonable, and maybe when I eventually get round to doing terminal recordings again I’ll use asciinema this time instead of termrec + my own <tty-player> element, as seen on https://chrismorgan.info/blog/make-and-git-diff-test-harness....)