[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Check for ANSI compliance
|
From: |
Ludovic Courtès |
|
Subject: |
Re: Check for ANSI compliance |
|
Date: |
Mon, 29 Jan 2024 17:44:16 +0100 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Hi,
Christian Miller <christian.miller@dadoes.de> skribis:
> I use the Emacs compilation mode (M-x compile).
>
> For example, the following "M-x compile RET guix build does-not-exist
> RET" would result to the following:
>
> -*- mode: compilation; default-directory: "~/" -*-
> Compilation started at Wed Jan 17 19:18:57
>
> guix build does-not-exist
> guix build: error: does-not-exist: unknown package
>
> Compilation exited abnormally with code 1 at Wed Jan 17 19:18:57
>
> It is not only visually, but it actually breaks a feature of the mode,
> too. The unknown package error is not detected as an error by the
> mode. I also had a case where it detected warnings as errors.
>
> Could we check for ANSI compliance instead of assuming it's presence?
That used to be the case until commit
672d3d4a87839b0692c307df0edb66cd16bcbf1a, which enabled colors even when
‘INSIDE_EMACS’ is set.
Pierre, do you remember what the rationale was?
Ludo’.