I wrote a blog post[1] breaking down tools to record terminal sessions just a couple weeks ago. I wasn't aware of this particular one but it looks like it's going to have issues with recording anything that requires user input.
My post describes how to make high quality recordings of terminal sessions that can be replayed in the terminal, or shared on the web. I'm defining high quality as recordings with zero typos, and relatively controlled timing between commands.
I'm going to assume this works well because all the stuff from Charm seems to, BUT its limitations are ... problematic. I think the techniques i list in the post combined with agg[2] or gifcast[3] to covert it to a gif would be a better solution for non-trivial cases.
I'll add notes about agg and gifcast to the post this evening hopefully.
My post describes how to make high quality recordings of terminal sessions that can be replayed in the terminal, or shared on the web. I'm defining high quality as recordings with zero typos, and relatively controlled timing between commands.
I'm going to assume this works well because all the stuff from Charm seems to, BUT its limitations are ... problematic. I think the techniques i list in the post combined with agg[2] or gifcast[3] to covert it to a gif would be a better solution for non-trivial cases.
I'll add notes about agg and gifcast to the post this evening hopefully.
[1]: https://weblog.masukomi.org/2022/10/11/recording_and_sharing...
[2]: https://github.com/asciinema/agg
[3]: https://github.com/dstein64/gifcast