From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Mattias =?UTF-8?Q?Engdeg=C3=A5rd?= Newsgroups: gmane.emacs.bugs Subject: bug#18109: 24.4.50; `compilation-error-regexp-alist-alist': wrong regexp for Maven Date: Wed, 9 Dec 2020 19:41:27 +0100 Message-ID: References: <5FFB3461-E756-4C09-9BFE-E0F9C840E533@acm.org> <133EE4BE-AD7E-4197-9888-1E4CCC47BB90@acm.org> Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2433"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Lars Ingebrigtsen , 18109-done@debbugs.gnu.org To: Filipp Gunbin Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Dec 09 20:42:34 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kn5MA-0000WH-7d for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 09 Dec 2020 20:42:34 +0100 Original-Received: from localhost ([::1]:42556 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kn5M9-0000vU-9c for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 09 Dec 2020 14:42:33 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60960) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kn4Qa-0008Gr-7X for bug-gnu-emacs@gnu.org; Wed, 09 Dec 2020 13:43:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:52768) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kn4QY-0002Ec-JS for bug-gnu-emacs@gnu.org; Wed, 09 Dec 2020 13:43:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kn4QY-00019Z-Gw for bug-gnu-emacs@gnu.org; Wed, 09 Dec 2020 13:43:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Mattias =?UTF-8?Q?Engdeg=C3=A5rd?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 09 Dec 2020 18:43:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 18109 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 18109-done@debbugs.gnu.org id=D18109.16075393654405 (code D ref 18109); Wed, 09 Dec 2020 18:43:02 +0000 Original-Received: (at 18109-done) by debbugs.gnu.org; 9 Dec 2020 18:42:45 +0000 Original-Received: from localhost ([127.0.0.1]:36081 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kn4QH-00018z-Em for submit@debbugs.gnu.org; Wed, 09 Dec 2020 13:42:45 -0500 Original-Received: from mail1444c50.megamailservers.eu ([91.136.14.44]:35038 helo=mail264c50.megamailservers.eu) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kn4QF-00018i-RT for 18109-done@debbugs.gnu.org; Wed, 09 Dec 2020 13:42:44 -0500 X-Authenticated-User: mattiase@bredband.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=megamailservers.eu; s=maildub; t=1607539356; bh=y5pgFO2gPuC6Ivjp0O7BTBSzzX5sVrXxPU/cIjrY2x0=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=aQKe0PbfaQQqIWmk6Yt/i3QFl9q2w7gNKpz0wo9C/tRfbknICuEfQ4GLxmNidbcqk 9eX+6lPR1/FcTb1qdCxqjkKqRvWJJsh0/+zJpMpsoCNQhrwkKmpkxwXnwiLlzgiJK6 K9+sSJzx9Z8M0bHPnE6oFIE/TmJZf+LzjIDRAOVs= Feedback-ID: mattiase@acm.or Original-Received: from [192.168.0.4] (c188-150-171-71.bredband.comhem.se [188.150.171.71]) (authenticated bits=0) by mail264c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id 0B9IgYEf020676; Wed, 9 Dec 2020 18:42:36 +0000 In-Reply-To: X-Mailer: Apple Mail (2.3445.104.17) X-CTCH-RefID: str=0001.0A782F23.5FD11A9C.009B, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.3 cv=bPlo382Z c=1 sm=1 tr=0 a=SF+I6pRkHZhrawxbOkkvaA==:117 a=SF+I6pRkHZhrawxbOkkvaA==:17 a=kj9zAlcOel0A:10 a=M51BFTxLslgA:10 a=R7GNrqYv_EcShI-FDagA:9 a=CjuIK1q_8ugA:10 X-Origin-Country: SE X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:195565 Archived-At: 7 dec. 2020 kl. 21.07 skrev Filipp Gunbin : > [...] I have a feeling that few in Java world care about how the > error parses in Emacs). Most likely. On the other hand, lack of interest in the output format = can also imply that it's unlikely to change. > I doubt that any modern-or-so Java IDE will parse any error messages, > given that build tools and compilers have APIs. 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. > - 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). > 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!