Closed der-eismann closed 1 year ago
While reading the build logs from summit, the output from moss is quite hard to read with stuff like this:
[02:03:51] [1;33mWARNING [0m Using non-standard configuration directory: /srv/avalanche/avalanche/state/work [02:03:51] [1;34mINFO [0m Stage success: create-root [02:04:03] [1;34mINFO [0m Stage success: fetch-upstreams [1;33mWARNING [0m Unable to discover Active State ID [1;34mINFO [0m Rebuilding indices on `repo0` [1;34mINFO [0m Added remote repo0 [02:04:03] [1;34mINFO [0m Stage success: configure-root [1;33mWARNING [0m Unable to discover Active State ID [0;mThe following packages will be installed [0;m [0;m[1macl[0;m[0;m - [0;m[0;m[0;35m2.3.1[0;m[0;m-[0;m[0;m[0;36m2[0;m [0;m[1mlibxcb[0;m[0;m - [0;m[0;m[0;35m1.15[0;m[0;m-[0;m[0;m[0;36m2[0;m [0;m[1mattr[0;m[0;m - [0;m[0;m[0;35m2.5.1[0;m[0;m-[0;m[0;m[0;36m2[0;m [0;m[1mlibxcb-devel[0;m[0;m - [0;m[0;m[0;35m1.15[0;m[0;m-[0;m[0;m[0;36m2[0;m [0;m[1mbash[0;m[0;m - [0;m[0;m[0;35m5.2.15[0;m[0;m-[0;m[0;m[0;36m5[0;m [0;m[1mlibxcrypt[0;m[0;m - [0;m[0;m[0;35m4.4.33[0;m[0;m-[0;m[0;m[0;36m3[0;m [0;m[1mboulder[0;m[0;m - [0;m[0;m[0;35m0.1[0;m[0;m-[0;m[0;m[0;36m32[0;m [0;m[1mlibxext[0;m[0;m - [0;m[0;m[0;35m1.3.5[0;m[0;m-[0;m[0;m[0;36m3[0;m [0;m[1mbrotli[0;m[0;m - [0;m[0;m[0;35m1.0.9[0;m[0;m-[0;m[0;m[0;36m3[0;m [0;m[1mlibxext-devel[0;m[0;m - [0;m[0;m[0;35m1.3.5[0;m[0;m-[0;m[0;m[0;36m3[0;m [0;m[1mbzip2[0;m[0;m - [0;m[0;m[0;35m1.0.8[0;m[0;m-[0;m[0;m[0;36m2[0;m [0;m[1mlibxml2[0;m[0;m - [0;m[0;m[0;35m2.10.3[0;m[0;m-[0;m[0;m[0;36m4[0;m
Would be great if it's possible to disable the colored output and have a better overview when reading the logs.
Detecting whether or not the output goes to a TTY is super simple: https://forum.dlang.org/thread/mailman.327.1386419696.3242.digitalmars-d-learn@puremagic.com
The usual approach is:
While reading the build logs from summit, the output from moss is quite hard to read with stuff like this:
Would be great if it's possible to disable the colored output and have a better overview when reading the logs.