From 899c2af576124df2918fd2ae976434df0ebbae5b Mon Sep 17 00:00:00 2001 From: _ov4 Date: Wed, 21 Oct 2026 14:06:54 +0000 Subject: feat(driver): color diagnostics like gcc with -fdiagnostics-color Add -fdiagnostics-color[=auto|always|never] and -fno-diagnostics-color. The default auto mode colors only a terminal stderr (TERM set and not dumb on Unix; a console that accepts VT sequences on Windows), so test harnesses, the desktop bundle and other pipes stay plain. Every diagnostic label now comes from cps::diagnosticPrefix, which emits gcc's default GCC_COLORS bytes: bold locus, bold red error/fatal error, bold magenta warning, bold cyan note. compilation terminated., runtime messages of the compiled program and lld output are unchanged. Co-Authored-By: Claude Opus 5.5 --- plugin/AGENTS/ARCH.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'plugin') diff --git a/plugin/AGENTS/ARCH.md b/plugin/AGENTS/ARCH.md index 0f585bb..eb97e63 100644 --- a/plugin/AGENTS/ARCH.md +++ b/plugin/AGENTS/ARCH.md @@ -70,7 +70,8 @@ profile does not change an existing terminal. Windows bash profiles and non-POSI Unix shells are outside the supported terminal set. Save cancellation starts nothing. Save or terminal setup failures show an English -error message; compiler and program diagnostics go directly to the terminal. +error message; compiler and program diagnostics go directly to the terminal, +where cpsc colors its own diagnostics like gcc. Terminal execution follows Code Runner's reuse behavior: users must finish or interrupt an interactive program with Ctrl+C before running another file. -- cgit v1.3.1-4-g156e