toolroom.color¶
Probe how footman forces colour for each installed tool, and regenerate
the colour data.
footman spawns over pipes (no PTY), so it forces colour into the tools it
spawns — by the environment (FORCE_COLOR/NO_COLOR) for the modern set, by
the tool's own switch for the few that ignore it. Which is which is probed,
not assumed: each tool is run with colour forced on and off, and the bytes
read, so a direction is recorded env, flag (like git's
-c color.ui=always), none, or unprobed (no trigger figured out).
Writes toolroom's _colordata.py, which the bridge reads for its forcing
table and the docs read for the support table — and only ever from a
--prefix, a fm toolroom.provision directory. A verdict is a claim about a
release, so it has to come from a release someone fetched on purpose:
without a prefix this machine's own binaries answer, at whatever versions
it happens to carry and missing whatever it never installed. That reads
fine as a table on a terminal, which is why it still prints one; it is not
something to check in.
| Parameter | Type | Default | Description |
|---|---|---|---|
--only=VALUE |
"" |
probe just this tool | |
--write |
flag | true |
regenerate toolroom's _colordata.py |
--prefix=VALUE |
"" |
probe binaries from this prefix's bin/ |