Whoops, it's the first time I use script so I wasn't aware that would be related to scriptreplay. Sorry for the unexpected influence ;)Recent commit that removed header timestamp from typescript output when --quiet option is defined broke scriptreplay. Trouble was that scriptreplay always skipped first line of the typescript. But --quiet makes that line to be part of what must be printed by scriptreplay.
As it comes to man page, what do you think of adding a note there to show why the start message isn't suppressed?Not sure about it. It seems like overkill... I have reverted Rui's change and fixed the man page. It seems better to keep things simple and stupid... it means keep typescript file completely independent on the --quit option (for the both, start and done messages).
Forgive my witless, what's the point of introducing a length? Doesn't we already know the header takes (and only takes) the first line?On 18 April 2017 at 11:23, Karel Zak <kzak@redhat.com> wrote:Anyway, I don't like officially supported file formats without any header. IMHO it would be really nice to add to the typescript: ### script(1) typescript; Version: util-linux v2.30; Date: 2017-04-18 12:10:43+0200 ... and maybe more information. The same for timing file.I agree. What comes to header data it should include header length in bytes. Something like ### script(1) typescript; Header Length: 104 Version: util-linux v2.30; Date: 2017-04-18 12:10:43+0200 As long it's easy to know how long to jump rest of the format does not really matter. Right.