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

[Mattias Engdegård]

6 okt. 2023 kl. 18.49 skrev Stefan Monnier <monnier@iro.umontreal.ca>:

> How 'bout we only activate a handful of rules, and then use a "low
> priority background" search for matches to the non-active rules and when
> we find such a match we bring it to the users' attention that maybe they
> should enable that extra rule?

"It looks like you are compiling a Pascal program using a Sun compiler from 
1989. Would you like me to parse the error messages for you?"

Even if we were to pull off the 'low priority background' part, it seems 
difficult to balance such a mechanism so that it's never annoying yet relevant 
when it needs to be.

In any case we would benefit from a better way to select rules. One problem is 
that packages (and users) go wild modifying both CERA and CERAA. Here is a 
patch that I'm not satisfied with but tries to make CERA easier to customise 
interactively.

Its main limitation is assuming that explicit rule specs precede symbols that 
refer to CERAA, which makes some kind of sense (new rules are added for a 
reason so they should take priority) but may not correspond to reality. Not 
sure what to do about that, but at least it's a start.

cera-type.diff
Description: Binary data