unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70794@debbugs.gnu.org
Subject: bug#70794: 30.0.50; Add Rust compilation regex
Date: Wed, 15 May 2024 15:10:02 +0200	[thread overview]
Message-ID: <q6appvzmmlhwxilvsokxtsyfoccj4pcqamsmh77o2ekdirzwnx@egqgkt5sawk5> (raw)
In-Reply-To: <86le4g3f5z.fsf@gnu.org>

On Sat, May 11, 2024 at 11:51:04AM GMT, Eli Zaretskii wrote:
>> 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?

Hi Eli:

Typically they look like this:

```
error[E0425]: cannot find function `ruun` in module `broot::cli`
   --> src/main.rs:6:23
    |
6  |     match broot::cli::ruun() {
    |                       ^^^^ help: a function with a similar name exists: `run`
    |
   ::: /tmp/broot/src/cli/mod.rs:49:1
    |
49 | pub fn run() -> Result<Option<Launchable>, ProgramError> {
    | -------------------------------------------------------- similarly
    named function `run` defined here
```

or

```
error: cannot find macro `deebug` in this scope
    --> src/main.rs:5:5
     |
5   |     deebug!("env::args(): {:#?}", std::env::args().collect::<Vec<String>>());
     |     ^^^^^^ help: a macro with a similar name exists: `debug`
     |
    ::: /home/ergo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/log-0.4.21/src/macros.rs:154:1
     |
154 | macro_rules! debug {
     | ------------------ similarly named macro `debug` defined here
```

```
warning: crate-level attribute should be an inner attribute: add an exclamation mark: `#![foo]`
  --> src/main.rs:3:1
   |
3 | #[feature(proc_macro_diagnostic)]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(unused_attributes)]` on by default
```

Two details:

1. As you can see the [] is optional
2. The path is always relative to project's root






  reply	other threads:[~2024-05-15 13:10 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 [this message]
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=q6appvzmmlhwxilvsokxtsyfoccj4pcqamsmh77o2ekdirzwnx@egqgkt5sawk5 \
    --to=bug-gnu-emacs@gnu.org \
    --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).