compose/cmd
Nicolas De Loof cccb9f1f7e cli: display.Mode always resolves to the mode actually rendered
The display.Mode package global was left as "auto" on the most common
path (auto mode with an interactive or redirected terminal), so readers
like `up`'s NavigationMenu gate saw an unresolved value; that gate also
compared against the string literal "plain" instead of the constant.
applyDisplayMode wrote a mode that selectEventProcessor could then
contradict (--ansi always with a redirected stderr rendered Plain while
Mode said tty).

selectEventProcessor becomes the single resolution point: every branch
assigns the mode matching the renderer it returns, so after command
setup the global never holds ModeAuto. applyDisplayMode loses its
redundant writes and its misleading name (now applyAnsiMode); the
contract is documented on the Mode variable, and the existing
selectEventProcessor tests now pin the resolved mode for every branch.

Side effect, deliberate: with stderr redirected (auto -> plain
rendering) the navigation menu is no longer offered; it used to slip
through because Mode still read "auto".

Part of #14074 (section E).

Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
2026-08-20 15:10:15 +02:00
..
cmdtrace golangci-lint: use gci formatter instead of goimports 2025-12-01 12:21:50 +01:00
compatibility modernize some code 2026-02-12 15:31:35 +01:00
compose cli: display.Mode always resolves to the mode actually rendered 2026-08-20 15:10:15 +02:00
display cli: display.Mode always resolves to the mode actually rendered 2026-08-20 15:10:15 +02:00
formatter feat(ps): add ENGINE column gated on label presence 2026-08-17 10:34:46 +02:00
prompt golangci-lint: use gci formatter instead of goimports 2025-12-01 12:21:50 +01:00
main.go feat: add Docker Desktop Logs view hints and navigation shortcut 2026-04-10 15:26:08 +02:00