From: Eli Zaretskii <eliz@gnu.org>
To: Ergus <spacibba@aol.com>
Cc: 70794@debbugs.gnu.org
Subject: bug#70794: 30.0.50; Add Rust compilation regex
Date: Sat, 11 May 2024 11:51:04 +0300 [thread overview]
Message-ID: <86le4g3f5z.fsf@gnu.org> (raw)
In-Reply-To: <87y18nsp84.fsf@aol.com> (bug-gnu-emacs@gnu.org)
> Date: Mon, 06 May 2024 03:28:43 +0200
> From: Ergus via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Recently working with rust I have noticed that emacs does not recognizes
> the rust/cargo error patterns.
>
> Considering that emacs has now the rust-ts-mode, it may worth adding
> the rust/cargo error patterns to compile when using that mode
>
> In my system so far I have this:
>
> ```
> (with-eval-after-load 'rust-ts-mode
> (with-eval-after-load 'compile
> (add-to-list
> 'compilation-error-regexp-alist-alist
> `(cargo
> "\\(?:\\(?4:error\\)\\|\\(?5:warning\\)\\):[^\0]+?--> \\(?1:[^:]+\\):\\(?2:[[:digit:]]+\\):\\(?3:[[:digit:]]+\\)"
> 1 2 3 (5)
> nil
> (5 compilation-warning-face)
> (4 compilation-error-face)))
>
> (add-to-list 'compilation-error-regexp-alist 'cargo)))
>
> ```
>
> Maybe a more frequent rust user has a more general regex to
> recommend. But this one works for me.
>
> WDYT?
Thanks, but could you please also send the examples of Rust messages,
because we need to add them to etc/compilation.txt?
next prev parent reply other threads:[~2024-05-11 8:51 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 [this message]
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
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=86le4g3f5z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70794@debbugs.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).