I was using this for a while; until I discovered the 'script' and 'scriptreplay' commands that come with most unix systems.
You can start recording by running: `script -t timingfile typescript`.
Your screen contents are recorded into the file `typescript` and the timing into `timingfile`.
You can play back by running: `scriptreplay -t timingfile typescript`
Check out the script man page for more cool things; like streaming live by using a fifo.
> You can start recording by running: `script -t timingfile typescript`. Your screen contents are recorded into the file `typescript` and the timing into `timingfile`.
Beware `-t` it's a non-standard (as much as script is considered a standard) extension:
* on OpenBSD there is no `-t` (or any other option aside from `-a` "append to existing typescript file")
* on FreeBSD and OSX `-t` specifies the flush time interval (in seconds, defaulting to 30) (on FreeBSD > 9.2 `-r` will save IO and timing data)
* on older linux distros it's a flag to output timing data to stderr
And scriptreplay is linux-only, NetBSD 2 and FreeBSD can replay sessions with `script -p`
script and scriptreplay are awesome, but this isn't exactly the same thing. The docs clearly state "asciinema was inspired by script (and scriptreplay) commands".
The magic of asciinema is all about playback in the browser. In fact you can combine the two, for example, you can play back a script file, and then playback the playback in asciinema:
Now that I think about it, it would be cool if asciinema could directly load files created by script. I'm not sure if there's any difference between the two capture tools.
You can start recording by running: `script -t timingfile typescript`. Your screen contents are recorded into the file `typescript` and the timing into `timingfile`.
You can play back by running: `scriptreplay -t timingfile typescript`
Check out the script man page for more cool things; like streaming live by using a fifo.