There's also this, if anybody's interested: Preserving Command Line Workflow for a Package Management System using ASCII DAG Visualization(2018) [0] It's a pa

There's also this, if anybody's interested: Preserving Command Line Workflow for a Package Management System using ASCII DAG Visualization(2018) [0] It's a paper about implementing a new ASCII graph format for dependency management, and it compares existing ASCII graph formats at the front of the paper. I actually found interesting that many use-cases of ASCII graphs have diverse requirements that one format can't rule all. In particular, usually dependency trees are deep and wide, while git histories are... relatively short and less complex. Git ASCII graphing format is perfect for denoting graphs without ambiguity, but it becomes too long for most complex graphs, and that's where the paper comes in. Just a rant, not really super-related... but worth a mention. [0]: http://www.idav.ucdavis.edu/~ki/publications/graphterm-preprint.pdf http://www.idav.ucdavis.edu/~ki/publications/graphterm-prepr...