From a0556b861f2667a49ded048c9cfac88defff8c5f Mon Sep 17 00:00:00 2001 From: Teknium <127238744+teknium1@users.noreply.github.com> Date: Wed, 6 May 2026 03:58:20 -0700 Subject: [PATCH] fix(tui): restore gap before duration when verb segment is hidden MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The verb-padding change dropped the leading space in durationSegment on the assumption that the verb's trailing pad always supplies the gap. But the unicode spinner style sets showVerb=false, making verbSegment an empty string — in that mode the output would become `{frame}· {duration}` with no separator. Add the space back; harmless when the verb segment is shown (its trailing pad still provides the gap). --- ui-tui/src/components/appChrome.tsx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/ui-tui/src/components/appChrome.tsx b/ui-tui/src/components/appChrome.tsx index 39e66984f7..29e663a47f 100644 --- a/ui-tui/src/components/appChrome.tsx +++ b/ui-tui/src/components/appChrome.tsx @@ -110,7 +110,11 @@ function FaceTicker({ color, startedAt }: { color: string; startedAt?: null | nu const { frame } = renderIndicator(style, tick) const verb = VERBS[verbTick % VERBS.length] ?? '' const verbSegment = showVerb ? ` ${padVerb(verb)}` : '' - const durationSegment = startedAt ? `· ${padTickerDuration(now - startedAt)}` : '' + // Leading space keeps a gap between the frame and the duration when the + // verb segment is hidden (e.g. `unicode` spinner style). When the verb + // IS shown, its trailing padding already provides the gap, so the extra + // space is harmless. + const durationSegment = startedAt ? ` · ${padTickerDuration(now - startedAt)}` : '' return (