From: "Mattias Engdegård" <mattiase@acm.org>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 18109@debbugs.gnu.org
Subject: bug#18109: 24.4.50; `compilation-error-regexp-alist-alist': wrong regexp for Maven
Date: Sun, 6 Dec 2020 10:32:27 +0100 [thread overview]
Message-ID: <E406A39A-5437-488A-A40A-582AC59D9DAE@acm.org> (raw)
In-Reply-To: <m2im9fj3lx.fsf@fastmail.fm>
5 dec. 2020 kl. 23.21 skrev Filipp Gunbin <fgunbin@fastmail.fm>:
> Now the regexp seems to catch both prefixed and non-prefixed messages,
> what else should be resolved here?
Ah, yes. Apart from the examples in compilation.txt, I could not find any evidence for non-prefixed messages ever being emitted. Since I'm not a Maven user myself, it would be useful to know if the non-prefixed example was just an oversight or an actual occurrence.
It is not a major problem but I like doing a proper work. Having patterns that match more than their strict minimum can be troublesome for two reasons: a regexp may accidentally catch a message intended for another pattern, and it may slow down message matching. Both have been issues several times in the past, which is why I'm wary of having too-loose regexps in the list.
next prev parent reply other threads:[~2020-12-06 9:32 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 [this message]
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
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=E406A39A-5437-488A-A40A-582AC59D9DAE@acm.org \
--to=mattiase@acm.org \
--cc=18109@debbugs.gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=larsi@gnus.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).