Hi all, If I may, NO_COLOR approach seems to be rather straightforward to me, as per description on their homepage[1] - make all software supporting it behave as colors are an opt-in feature, thus disabled by default. And that's all there is to it. Software which is able to but does not show any colors by default does not need to care at all, as colors are an opt-in feature there already, so NO_COLOR serves no purpose. On the other hand, software which does enable (at least some) color by default, without user explicitly setting anything but requiring opt-out to disable color instead, should treat NO_COLOR precisely as that user requested opt-out, with an obvious convenience for the user being able to set NO_COLOR globally once and have all the programs supporting it recognize it as color opt-out exactly, without a need for the user to opt-out in each and every program separately (and differently). So, the whole point is make the default value be "no color" for each and every application consistently, where user (and _not_ developer) needs to opt-in in order to enable colors (in each and every application where colors are in fact still desired). Regards, Buga -- [1]: https://no-color.org/
