From: Filipp Gunbin <fgunbin@fastmail.fm>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 18109-done@debbugs.gnu.org
Subject: bug#18109: 24.4.50; `compilation-error-regexp-alist-alist': wrong regexp for Maven
Date: Thu, 10 Dec 2020 16:12:25 +0300 [thread overview]
Message-ID: <m2ft4d3iva.fsf@fastmail.fm> (raw)
In-Reply-To: <DF292D98-0CAB-4867-AC87-2D25CE0D9950@acm.org> ("Mattias Engdegård"'s message of "Wed, 9 Dec 2020 19:41:27 +0100")
On 09/12/2020 19:41 +0100, Mattias Engdegård wrote:
> Quite possible, but the very emission of formalised messages to
> stdout/stderr means that this mode of usage is still acknowledged as
> somewhat common and useful.
Yes, sure.
>> - did we have really that much problems caused by bad
>> performance of compilation regexps? Because if we did, then maybe we
>> should look at other approaches, like trying to detect the compiler
>> used, and narrow the set of regexps based on it.
>
> This is hard to do in any practical way, not the least because a
> single message buffer may consist of the combined output of dozens of
> different tools -- compilers, linters, build tools, spell checkers,
> testing, stack traces, packaging, and so on. Not to mention the
> practical difficulty of going from the string 'make' to 'GCC version
> 11.2'.
>
> That things work reasonably anyway is very much thanks to the
> prevalence of a few fairly common formats, such as GNU (file:line:
> message).
Yes, btw I see that "gnu" regexp sometimes captures messages which I
expect to be captured by "javac" regexp. This is not that unexpected,
given the occasional similarity between formats... I'll look into that
later.
>> It's natural to expect
>> that many different people would edit these regexps when something
>> doesn't work for them, and expecting that you will always come and fix
>> the things up would not be very fair to you :-)
>
> Very considerate, thank you! There seems to be a fairly good flow of
> reports when something doesn't work. (A more modern and inviting
> bug-reporting system would probably help but that is a completely
> different matter.)
>
> I'm pushing the proposed tightening of gradle-kotlin because the
> principle is right, and even if the Java world internally prefer APIs
> for composing tools, a tighter regexp in Emacs helps performance and
> accuracy for other patterns. Loose regexps form a sort of tragedy of
> the commons.
>
> It seems that we also have forgotten to close the bug; doing that
> now. Thank you again for the insightful comments!
Thank you for careful work.
Filipp
prev parent reply other threads:[~2020-12-10 13:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 17:33 bug#18109: 24.4.50; `compilation-error-regexp-alist-alist': wrong regexp for Maven Filipp Gunbin
2014-07-26 7:22 ` Glenn Morris
2014-07-28 12:30 ` Filipp Gunbin
2014-08-03 15:12 ` Daniel Colascione
2020-09-09 11:16 ` Lars Ingebrigtsen
2020-12-03 14:59 ` Lars Ingebrigtsen
2020-12-04 18:11 ` Filipp Gunbin
2020-12-04 19:22 ` Mattias Engdegård
2020-12-05 22:21 ` Filipp Gunbin
2020-12-06 9:32 ` Mattias Engdegård
2020-12-06 14:22 ` Filipp Gunbin
2020-12-06 15:05 ` Mattias Engdegård
2020-12-06 15:25 ` Mattias Engdegård
2020-12-07 10:41 ` Filipp Gunbin
2020-12-07 13:49 ` Mattias Engdegård
2020-12-07 20:07 ` Filipp Gunbin
2020-12-09 18:41 ` Mattias Engdegård
2020-12-10 13:12 ` Filipp Gunbin [this message]
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=m2ft4d3iva.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=18109-done@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
/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).