Subject: Re: bug#58984: 29.0.50; M-x compile misinterprets libcheck error message format

From: Mattias Engdegård <[email-masked]>
Date: Fri, 4 Nov 2022 18:49:08 +0100

4 nov. 2022 kl. 18.08 skrev Basil L. Contovounesios <[email-masked]>:

> Like this compile log, for instance?

Thank you, I didn't pay enough attention. Let's look at:

> itree-tests.c:71:F:insert1:test_insert_1:0: Assertion 'N_50.red' failed

This doesn't quite conform to GNU message standards, does it? For it to have the

  [PROGRAM:]FILE:LINE: MESSAGE

form, there should be a space before the message (that is, before the 'F'). Otherwise parsing these things become almost impossible with all the possible variations, file names containing spaces and colons and so on. Currently, the machinery interprets "tree-tests.c" as the program name and "71:F:insert1:test_insert_1" as the file which is of course nonsense.

Any hope the tool can have its output format adjusted?