4 ms·
So you want every developer to spend time on both color and non-color options but are not willing to contribute a patch for that?
by cat_plus_plus 3y ago
So you want every developer to spend time on both color and non-color options but are not willing to contribute a patch for that?
- alpaca128 3y agoAside from your uncharitable interpretation: it is really not difficult or time-consuming to support this. It's just setting and checking a single boolean flag, in fact it may simply just be a few lines at startup if the tool already supports color options via cli args.
- JdeBP 3y agoIndeed, if one uses the termcap or terminfo libraries (or the likes of unibilium) to obtain the control sequences for colour from those databases, instead of hardwiring them into the source code of print statements, one gets the TERM=dumb convention implemented entirely for free.
- cat_plus_plus 3y agoIn this case it seems pretty easy to contribute a patch? Mature projects have unit and screendiff test suites that need to be updated and extended to verify the new case, so it might not be THAT easy even for a trivial change.
- account42 3y ago> Mature projects have unit and screendiff test suites Good joke.
- kps 3y agoI have no problem contributing patches, but nothing I currently use regularly is ill-behaved. Not using colour is no work at all. Using colour correctly is a fair bit of work, and few programs do so; practically none check whether the terminal background is dark or light before emitting a dark blue or light yellow.