authorgravatar for mlugg@mlugg.co.ukMatthew Lugg <mlugg@mlugg.co.uk> 2025-12-06 14:22:47+00:00
committergravatar for mlugg@mlugg.co.ukMatthew Lugg <mlugg@mlugg.co.uk> 2025-12-06 14:22:47+00:00
logdb15df5daa3e5e93ff1085e7a43999f0bb61938b
treec6a3625780085e9404dedf57da0e677c7d6dbcce
parent65922a2d4319ca2e9f3e67650d018e269d018a77
signaturelock-open Commit is signed but in an unrecognized format.

build_runner: don't dim the tree line of reused step

This was presumably unintentional, as the old behavior looked quite odd when you noticed it. All of the line-drawing characters ought to be the same color; only the step name/status is dimmed when a step is "reused" (i.e. appears multiple times in the tree).

1 files changed, 2 insertions(+), 1 deletions(-)

lib/compiler/build_runner.zig+2-1
...@@ -1186,7 +1186,6 @@ fn printTreeStep(...@@ -1186,7 +1186,6 @@ fn printTreeStep(
1186 if (skip) return;1186 if (skip) return;
1187 try printPrefix(parent_node, stderr, ttyconf);1187 try printPrefix(parent_node, stderr, ttyconf);
11881188
1189 if (!first) try ttyconf.setColor(stderr, .dim);
1190 if (parent_node.parent != null) {1189 if (parent_node.parent != null) {
1191 if (parent_node.last) {1190 if (parent_node.last) {
1192 try printChildNodePrefix(stderr, ttyconf);1191 try printChildNodePrefix(stderr, ttyconf);
...@@ -1198,6 +1197,8 @@ fn printTreeStep(...@@ -1198,6 +1197,8 @@ fn printTreeStep(
1198 }1197 }
1199 }1198 }
12001199
1200 if (!first) try ttyconf.setColor(stderr, .dim);
1201
1201 // dep_prefix omitted here because it is redundant with the tree.1202 // dep_prefix omitted here because it is redundant with the tree.
1202 try stderr.writeAll(s.name);1203 try stderr.writeAll(s.name);
12031204