GNU bug report logs - #60830
30.0.50; The *Compilation* buffer does not recognize Lua errors

Previous Next

Package: emacs;

Reported by: Rudolf Adamkovič <salutis <at> me.com>

Date: Sun, 15 Jan 2023 11:35:01 UTC

Severity: wishlist

Found in version 30.0.50

Done: Stefan Kangas <stefankangas <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Mattias Engdegård <mattias.engdegard <at> gmail.com>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 60830 <at> debbugs.gnu.org, Rudolf Adamkovič <salutis <at> me.com>, Stefan Kangas <stefankangas <at> gmail.com>
Subject: bug#60830: 30.0.50; The *Compilation* buffer does not recognize Lua errors
Date: Fri, 6 Oct 2023 16:00:13 +0200
6 okt. 2023 kl. 15.21 skrev Stefan Monnier <monnier <at> iro.umontreal.ca>:

> 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.





This bug report was last modified 1 year and 211 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.