Re: subtle problem of font-lock in *compilation* buffer

[Chong Yidong <cyd@stupidchicken.com>]

Richard Stallman <rms@gnu.org> writes:

>     > That is perhaps because of "1:0:1".
>
>     How can the compilation font-lock pattern distinguish this from a
>     legitimate error message?
>
> How about by the spaces in the "file name"?

It would wrongly reject compilation messages for file names containing
spaces.


Kenichi Handa <handa@m17n.org> writes:

> I don't know whqether it's uncommon or not, but if a packages uses
> libtool with "-version-info M:N:L" argument, the above line
> appears.  It may be too ad hoc but we can tell font-lock
> that a line matching with the regexp "-version-info [0-9]"
> is not an error message (if font-lock accepts such a
> request).

I don't see a straightforward way of doing this, but I guess it's
worth a shot.

>  Or, more generally, we may be able tell that a line matching with
> "^/bin/sh " is not an error message.

This would be wrong if you are compiling the file /bin/sh (unlikely as
that may seem).