From: "Mattias Engdegård" <mattiase@acm.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 58984@debbugs.gnu.org
Subject: bug#58984: 29.0.50; M-x compile misinterprets libcheck error message format
Date: Sun, 6 Nov 2022 15:26:51 +0100 [thread overview]
Message-ID: <6252DE05-F84F-4A81-BD06-3F4CF7AFCD08@acm.org> (raw)
In-Reply-To: <87zgd4uvu7.fsf@tcd.ie>
6 nov. 2022 kl. 13.10 skrev Basil L. Contovounesios <contovob@tcd.ie>:
> The only alternative format I'm aware of is after compiling the test
> runner in CK_SUBUNIT mode instead of CK_NORMAL or CK_ENV.
If you like but I rather thought about fixing libcheck. Would something break if we added a space to the format string in `tr_str`? Ask the maintainers?
> In any case the feature request was to support Check's default output
> (what we do with our small manual test suite is largely
> inconsequential), so if that's too difficult and brittle for few gains,
> we can close this as wontfix.
You decide -- I don't think it's worth the trouble to add more contortions to the already much too complex `gnu` compilation-mode rule, if that is even possible without breaking something else or introducing major regexp backtracking points...
next prev parent reply other threads:[~2022-11-06 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 13:07 bug#58984: 29.0.50; M-x compile misinterprets libcheck error message format Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-04 11:30 ` Mattias Engdegård
2022-11-04 17:08 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-04 17:49 ` Mattias Engdegård
2022-11-06 12:10 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-06 14:26 ` Mattias Engdegård [this message]
2022-11-08 18:24 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-09 11:14 ` Mattias Engdegård
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6252DE05-F84F-4A81-BD06-3F4CF7AFCD08@acm.org \
--to=mattiase@acm.org \
--cc=58984@debbugs.gnu.org \
--cc=contovob@tcd.ie \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.