Subject: bug#60830: 30.0.50; The *Compilation* buffer does not recognize Lua errors

From: Mattias Engdegård <[email-masked]>
Date: Fri, 6 Oct 2023 16:00:13 +0200

6 okt. 2023 kl. 15.21 skrev Stefan Monnier <[email-masked]>:

> Can we rely on the ordering in `compilation-error-regexp-alist` to give
> precedence to the other rules?

Currently the ordering in `compilation-error-regexp-alist` (CERA for short) is the one used, but perhaps you mean the ordering in `compilation-error-regexp-alist-alist` (CERAA)?

I suppose we could compute a permutation of CERA that is consistent with CERAA and cache it to avoid doing it for every call to `compilation-parse-errors`, but what to do about non-symbol elements in CERA?

It's easiest to keep letting the user assume responsibility for ordering CERA correctly if customised. That said, the customisation mechanism doesn't work well for CERA. Perhaps it would be better to have a list of desired changes.