TDRERECORD(1)

📦 version 2.2, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 TDRERECORD(1) 💖

okay bestie, so you know termdebug? yeah, the whole terminal-debugging suite? this is the page for tdrerecord, one of its tools. buckle up. 🎀

✨ NAME ✨

tdrerecord — rerecord output of a terminal program 🦋

✨ SYNOPSIS ✨

tdrerecord [OPTIONS] RECORDING

✨ DESCRIPTION ✨

so basically tdrerecord re-records the output of a terminal program. how? by replaying the input from a recording. that's the whole trick. 💅

which means: you take an existing recording, you change how the program behaves, and boom — you get a brand new recording built from the exact same input. slay.

and if you don't pass any options at all? it just drops the recording into a file named tdrecord-year-month-day@hour:minute:second. cute, right? timestamped and everything. ⭐

⚠️ okay so real talk, this part matters. tdrerecord does not check whether the output conforms to the recorded output. that's lowkey dangerous, because the input may not be in sync with the output. and depending on what the program being run is actually capable of doing, this can cause data corruption. not the fun kind. 😭

✨ OPTIONS ✨

tdrerecord accepts the following options:

  • -h, --help — shows you a short help message. quick little "what do I do" moment. 🫶
  • -V, --version — prints version and copyright info. the receipts. 👑
  • -d dir, --directory=dir — makes the recording inside directory dir. heads up though: this option can not be used together with the -o/--output option. pick a lane bestie. 🙈
  • -o file, --output=file — saves the output into file. and yes, this one can not be used together with the -d/--directory option. same energy, opposite direction. 💀
  • -l, --no-strip-location-reports — do not remove ANSI cursor location reports from the recorded client input. normally these reports get stripped, because they're generated on request by the client program. if you leave them in the client input you'll end up with duplicate location reports, which is, like, very likely to confuse the client. but — plot twist — sometimes you actually need to keep these strings, for example if they were not generated in response to a client request. so use it when it's giving necessary. 🌸

and one more thing, super important: to stop tdrerecord from interpreting file names that start with a dash as options, you can drop a double dash (--). after that, tdrerecord will interpret any following arguments as files to read. the ultimate "no more options, we're just doing files now" barrier. periodt. ✨

🐛 BUGS 🐛

if you think you found a bug, first please check that you're running the latest version of termdebug <http://os.ghalkes.nl/termdebug>. and when you report it, please include a minimal example that demonstrates the problem. minimal!! we love a reproducible queen. 💜

👑 AUTHOR 👑

G.P. Halkes <termdebug@ghalkes.nl>

Copyright © 2010,2012-2013 G.P. Halkes

termdebug is licensed under the GNU General Public License version 3.

for more details on the license, see the file COPYING in the documentation directory. on Un*x systems this is usually /usr/share/doc/termdebug.

🌈 SEE ALSO 🌈

termdebug(1), tdrecord(1), tdreplay(1), tdview(1), tdcompare(1)

okay that's the whole page bestie, you're fully caught up 🎀 this was version 2.2, dated 2013/03/03 — and it's from the termdebug family. go rerecord something iconic. mwah. 💖✨🦋

📦 where this page comes from