From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70794@debbugs.gnu.org, spacibba@aol.com
Subject: bug#70794: 30.0.50; Add Rust compilation regex
Date: Mon, 3 Jun 2024 18:59:20 +0200 [thread overview]
Message-ID: <09473128-D0DB-442C-8404-EE58A18F5A5B@gmail.com> (raw)
In-Reply-To: <86ikyqkmuo.fsf@gnu.org>
3 juni 2024 kl. 18.33 skrev Eli Zaretskii <eliz@gnu.org>:
> Fine by me (I don't use Rust), but is the rule really broken? What
> happens if you move it to the end?
It is indeed broken as written because it would match anything starting with 'warning:' to something that looks like an arrow further down the log which could be an unrelated message a megabyte away.
I could try to slap together a guess at what a better one would be but then again, I wouldn't use it myself (rarely use Rust and when I do it's one of those external packages which have their own patterns and more importantly active maintainers). Furthermore I don't have the time to go poking around in the rustc (or cargo?) source code to see what the message-emitting parts look like, which is very useful when adding patterns.
Even with the obvious fixes, the pattern would still be incomplete and not even match parts of the examples given. I'm happy to work with Rust users or package maintainers to work out details but I don't want to do a rush job now, nor delay Emacs 30.
next prev parent reply other threads:[~2024-06-03 16:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y18nsp84.fsf.ref@aol.com>
2024-05-06 1:28 ` bug#70794: 30.0.50; Add Rust compilation regex Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-11 8:51 ` Eli Zaretskii
2024-05-15 13:10 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 10:52 ` Eli Zaretskii
2024-05-31 17:15 ` Mattias Engdegård
2024-06-03 14:41 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-03 15:35 ` Mattias Engdegård
2024-06-03 14:54 ` Mattias Engdegård
2024-06-03 15:28 ` Eli Zaretskii
2024-06-03 16:22 ` Mattias Engdegård
2024-06-03 16:33 ` Eli Zaretskii
2024-06-03 16:59 ` Mattias Engdegård [this message]
2024-06-04 22:06 ` Stefan Kangas
2024-06-05 22:56 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-06 7:34 ` Stefan Kangas
2024-06-03 22:36 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-04 14:33 ` Eli Zaretskii
2024-06-03 15:30 ` Eli Zaretskii
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=09473128-D0DB-442C-8404-EE58A18F5A5B@gmail.com \
--to=mattias.engdegard@gmail.com \
--cc=70794@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=spacibba@aol.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).