We have a lot here which this list is exclusively TUI programs.

https://terminaltrove.com/categories/tui

and another list which are terminal tool of the week where some TUIs are complex, like dolphie, kaskade, trippy or pug for example.

https://terminaltrove.com/tool-of-the-week/

https://terminaltrove.com/dolphie/

https://terminaltrove.com/kaskade/

https://terminaltrove.com/trippy/

https://terminaltrove.com/pug/

The GitHub CLI (https://cli.github.com/) uses Bubble Tea. There's no good way to find popular dependents, but you can browse https://github.com/charmbracelet/bubbletea/network/dependent... to see GitHub repos that import the module.

I similarly haven't used them, but vhs[1] looks very cool and useful (at least for my purposes, where I like to have lots of terminal demos in my documentation).

[1]: https://github.com/charmbracelet/vhs

I'm using `gum` in my personal shell scripts when I want basic interaction (show a list, checkboxes, etc)

Good use case for Asciinema.

https://asciinema.org

https://github.com/asciinema/asciinema

EDIT: Looks like image generator might be from one of their own projects:

https://github.com/charmbracelet/vhs

It shows the CLI use, seems pretty useful to me.

Indeed. A screenshot of the resulting output would have been more useful.

Well, yes, the meaning can depend, although many sequences have standardized meanings. The format of the sequences itself is also standardized but of course, the terminals don't need to use it either! There has been lots of terminals that use their own bespoke control sequences.

Still, nowadays people who write new terminal emulators tend to approach with "do what xterm/libvte does" attitude which is quite sensible: very few people use actual, physical terminals anymore, and the software ones are, well, are generally based on xterm or libvte (or that third library I keep forgetting).

And when was the last time terminfo has been updated anyhow? Not to mention that it lacks info about modern features such as e.g. the version of Unicode used/supported by the terminal.

> Isn't it true that ANSI sequences can vary depending on the terminal emulator?

Yes, historically, many terminals were not even ANSI compatible. That is why the terminfo database (and its predecessor termcap) exist; for programs to look at the TERM environment variable, use that to look up the terminal’s capabilities in terminfo, and see what the terminal can and cannot do, and then choose to output whatever sequences the terminal does support. Normally, a program uses yet another library, like ncurses, to do this, but you can do it yourself if you want to, like in a shell script or similar. Outputting raw escape codes is wrong, since the correct way is so very easy.