You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For reference, two major implementations I have looked at in node ecosystem and linked from force-color.org do not follow the description on force-color.org. The primary use in both cases is levels 0-3 with some other values explicitly supported. I think in practice other environment variables like CLICOLOR_FORCE and NO_COLOR have simpler patterns of usage than FORCE_COLOR for forcing color on/off.
The node implementation mentions being inspired by the supports_color package. Levels 1-3 correspond to 16 colours, 256 colours, and 16M colours.
Just found out about this project (see astral-sh/uv#3955) which seems to be trying to document and standardize
FORCE_COLOR
s behavior.It seems like it would be helpful to specify the behavior to be compatible with major users.
Behaviors I've seen through a quick survey
FORCE_COLOR
is present and non-emptyFORCE_COLOR
is presentFORCE_COLOR
is present and bool-ishThe text was updated successfully, but these errors were encountered: