Skip to content

Fix regex pattern for tagged rust warnings in compilation output#122

Merged
CeleritasCelery merged 1 commit intoemacs-rustic:mainfrom
ensc:fix-121
Feb 12, 2026
Merged

Fix regex pattern for tagged rust warnings in compilation output#122
CeleritasCelery merged 1 commit intoemacs-rustic:mainfrom
ensc:fix-121

Conversation

@ensc
Copy link
Contributor

@ensc ensc commented Feb 7, 2026

Rust now emits warnings with optional tags (e.g., "warning[E0133]:"). Update the warning regex pattern to match the approach already used for error patterns, which handle the same tagged format.

The pattern now accepts optional content between 'warning' and the colon, matching the existing error pattern that handles 'error[^:]*:'.

Fixes: #121

Rust now emits warnings with optional tags (e.g., "warning[E0133]:").
Update the warning regex pattern to match the approach already used
for error patterns, which handle the same tagged format.

The pattern now accepts optional content between 'warning' and the
colon, matching the existing error pattern that handles 'error[^:]*:'.

Fixes: emacs-rustic#121

Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
@ensc
Copy link
Contributor Author

ensc commented Feb 8, 2026

I think, the CI errors

eask package
💡 Unmatched version `3.5`; it should be `3.4`
💡 URL header is optional, but it's often recommended
💡 Unmatched keyword `languages`; add `(keywords "languages")` to Eask-file or consider removing it
💡 Unmatched dependency `emacs`; add `(depends-on "emacs")` to Eask-file or consider removing it
💡 Unmatched dependency `let-alist`; add `(depends-on "let-alist")` to Eask-file or consider removing it
💡 Unmatched dependency `flycheck`; add `(flycheck "VERSION")` to package-file or consider removing it
Loading package information... done ✓
- [1/1] Installing package-build (20260115.1042)... done ✓
Building artifact rustic (3.5)...

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
string-match("\\`\\(http\\)://\\(?:codeberg\\.org\\|git\\(?:\\.sr\\.ht\\|\\..." nil)

are caused by something else (missing metadata required by recent eask?)

@CeleritasCelery
Copy link
Contributor

yes, I just ran the CI and it is failing. It has not been run in a while so something is broken.

@CeleritasCelery CeleritasCelery merged commit cb013cd into emacs-rustic:main Feb 12, 2026
0 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"warning[...]: ..." style compile messages not recognized

2 participants