Bug#886927: ITP: tlog -- Terminal I/O recording and playback package.

[Adam Borowski <kilobyte@angband.pl>]

On Fri, Jan 12, 2018 at 08:53:35AM +0100, Andrew Shadura wrote:
> > Yay, yet another incompatible format.
[...]
> > I haven't looked if Asciinema grown a local format when I wasn't looking,
> > either.
> 
> Asciinema does, indeed, have a local format, JSON-based:

Thank you; I haven't watched it closely nor, to be honest, really worked on
my library in the last decade: 0.16 in 2008, 0.17 in 2014, 173 commits
pending but an unanswered "time for a new release" request from Mar 2017...

> {
>   "command": null,
>   "height": 22,
>   "title": "demo",
>   "duration": 37.608602,
>   "stdout": [
>     [
>       0.061412,
>       "\u001b]0;\u0007$ "
>     ],
>     …
>     ]
>   ],
>   "version": 1,
>   "width": 80,
>   "env": {
>     "SHELL": "/bin/bash",
>     "TERM": "xterm-256color"
>   }
> }

Wait, what?  It sends height when it's needed, at the start, but doesn't
send width or format's version until after the whole stream is over?

How are consumers supposed to take it, especially when it's still being
recorded, which is a major use case for tools like this?

This ITP (tlog) for example supports sending the data to syslog -- I don't
think anyone would be interested with having to wait till the end to send
all prior entries in one go.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Imagine there are bandits in your house, your kid is bleeding out,
⢿⡄⠘⠷⠚⠋⠀ the house is on fire, and seven big-ass trumpets are playing in the
⠈⠳⣄⠀⠀⠀⠀ sky.  Your cat demands food.  The priority should be obvious...