no_color config key is inert; honor it and add a --color flag #171
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
fj config set no_color trueis accepted (no_coloris inKNOWN_KEYS) but read nowhere; color is decided solely by thesupports-colorcrate (isatty plusNO_COLOR/FORCE_COLOR). The documented setting is a silent no-op, and there is no per-invocation override (e.g. force color intoless -R, or strip it where the crate would still colorize).Acceptance criteria
no_colorconfig value is honored in the color decision.--color <auto|always|never>flag overrides config and env (auto= today's behavior).--colorflag >NO_COLOR/FORCE_COLORenv >no_colorconfig > isatty.no_color=truesuppresses color (guards against re-introducing the dead key).Value
Correctness (the setting finally works) plus scripting / UX control over color in pipes and pagers.
Priority
p1 (small, low-risk, fixes a latent bug, global).
Dependencies / sequencing
None.
Overlap
None.