I would say that ttyrec is worth keeping.
First, the RC bug(s) are trivially fixable, all it takes is changing a
simple flag, a fix is in the BTS for five freaking years.
Ttyrec is used quite a bit, especially among NetHack and MUD players, so at
very least something which reads ttyrec's format should be available in the
archive. Script's format is incompatible (but it could be changed to
read/write ttyrec files).
Functionality-wise, script has the following flaws:
* it needs two separate files for a recording (fragile and unwieldy, unfit
for repositories you can download from)
* stderr is lost; any output to stderr from the session inside will break
the playback as well
* playback is non-interactive
Quoting script's manpage:
Certain interactive commands, such as vi(1), create garbage in the
typescript file. Script works best with commands that do not
manipulate the screen, the results are meant to emulate a hardcopy
terminal.
This is the opposite of ttyrec, which uses an opaque format, unusable for
reading as text but good for recording full-screen interactive sessions.
If having an upstream is so important, heck, I've written a compatible
recorder/graphical player myself; it's quite heavyweight as it focuses on
GUI and win32 support but could be easily turned into a drop-in replacement
with bells and whistles.
And there's ipbt too (not packaged for Debian), which has good playback (no
recording).
--
1KB // Microsoft corollary to Hanlon's razor:
// Never attribute to stupidity what can be
// adequately explained by malice.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
