From: "Mattias Engdegård" <mattiase@acm.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 56249@debbugs.gnu.org, "Rudolf Adamkovič" <salutis@me.com>
Subject: bug#56249: 29.0.50; Compilation buffer parsing "ERROR:" incorrectly
Date: Thu, 30 Jun 2022 13:08:51 +0200 [thread overview]
Message-ID: <49871E8E-1302-41A3-9917-EEEBEA6F7B44@acm.org> (raw)
In-Reply-To: <875ykifrov.fsf@gnus.org>
30 juni 2022 kl. 11.04 skrev Lars Ingebrigtsen <larsi@gnus.org>:
> It looks pretty useful to add this to compile.el anyway, so I've now
> done so.
All right, but do you even know what is emitting the message? Gradle is just a build system, isn't it?. And given that, is this how source-located messages from that tool are generally reported or is it some kind of special case? (Cf. GCC C-language errors vs. Make syntax errors vs. Bash syntax errors vs. ld errors etc, all of which are routinely emitted from a single `make` command.)
If you still think it's a good idea, how about adding a test case for this new rule to `compile-tests--test-regexps-data`, as well as an example to etc/compilation.txt?
next prev parent reply other threads:[~2022-06-30 11:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 7:04 bug#56249: 29.0.50; Compilation buffer parsing "ERROR:" incorrectly Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-27 8:09 ` Lars Ingebrigtsen
2022-06-28 17:36 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-29 9:53 ` Lars Ingebrigtsen
2022-06-29 12:16 ` Mattias Engdegård
2022-06-29 12:28 ` Lars Ingebrigtsen
2022-06-29 15:43 ` Mattias Engdegård
2022-06-29 19:47 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-29 20:09 ` Mattias Engdegård
2022-06-30 9:04 ` Lars Ingebrigtsen
2022-06-30 11:08 ` Mattias Engdegård [this message]
2022-07-05 16:04 ` Mattias Engdegård
2022-07-05 16:50 ` Lars Ingebrigtsen
2022-07-10 13:49 ` Mattias Engdegård
2022-07-11 9:48 ` Lars Ingebrigtsen
2022-07-11 10:31 ` Mattias Engdegård
2022-07-14 6:55 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49871E8E-1302-41A3-9917-EEEBEA6F7B44@acm.org \
--to=mattiase@acm.org \
--cc=56249@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=salutis@me.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).