>> Of course one way to deal with it is to do what we did for grep.el
>> (where a similar problem showed up) and match those lines explicitly
>> (and mark them as something else).
> Like that? It works for me.
Sounds good.
> (defvar compilation-mode-font-lock-keywords
> - '(;; configure output lines.
> + '(;; Don't highlight this as a compilation message.
> + ("^Compilation started at.*"
> + (0 '(face nil message nil help-echo nil mouse-face nil) t))
> + ;; configure output lines.
> ("^[Cc]hecking \\(?:[Ff]or \\|[Ii]f \\|[Ww]hether \\(?:to
> \\)?\\)?\\(.+\\)\\.\\.\\. *\\(?:(cached) *\\)?\\(\\(yes\\(?:
> .+\\)?\\)\\|no\\|\\(.*\\)\\)$"
> (1 font-lock-variable-name-face)
> (2 (compilation-face '(4 . 3))))
> @@ -408,9 +411,11 @@
> ("^\\([[:alnum:]_/.+-]+\\)\\(\\[\\([0-9]+\\)\\]\\)?[ \t]*:"
> (1 font-lock-function-name-face) (3 compilation-line-face nil t))
> (" --?o\\(?:utfile\\|utput\\)?[= ]?\\(\\S +\\)" . 1)
> - ("^Compilation \\(finished\\)"
> + ("^Compilation \\(finished\\).*"
> + (0 '(face nil message nil help-echo nil mouse-face nil) t)
> (1 compilation-info-face))
These two can be merged, can't they?
Stefan
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
