Mercurial > emacs
comparison lisp/progmodes/compile.el @ 86046:b182750e235e
Insert patterns from compilation-perl.el and compilation-weblint.el files.
author | Vinicius Jose Latorre <viniciusjl@ig.com.br> |
---|---|
date | Mon, 12 Nov 2007 18:29:05 +0000 |
parents | 786d3a985758 |
children | 4a1edf137bff 53108e6cea98 |
comparison
equal
deleted
inserted
replaced
86045:1fa61031bef4 | 86046:b182750e235e |
---|---|
337 (gcov-never-called | 337 (gcov-never-called |
338 "^ *\\(#####\\): *\\([0-9]+\\):.*$" | 338 "^ *\\(#####\\): *\\([0-9]+\\):.*$" |
339 nil 2 nil 2 nil | 339 nil 2 nil 2 nil |
340 (0 'default t) | 340 (0 'default t) |
341 (1 compilation-error-face prepend) (2 compilation-line-face prepend)) | 341 (1 compilation-error-face prepend) (2 compilation-line-face prepend)) |
342 | |
343 (compilation-perl--Pod::Checker | |
344 ;; podchecker error messages, per Pod::Checker. | |
345 ;; The style is from the Pod::Checker::poderror() function, eg. | |
346 ;; *** ERROR: Spurious text after =cut at line 193 in file foo.pm | |
347 ;; | |
348 ;; Plus end_pod() can give "at line EOF" instead of a | |
349 ;; number, so for that match "on line N" which is the | |
350 ;; originating spot, eg. | |
351 ;; *** ERROR: =over on line 37 without closing =back at line EOF in file bar.pm | |
352 ;; | |
353 ;; Plus command() can give both "on line N" and "at line N"; | |
354 ;; the latter is desired and is matched because the .* is | |
355 ;; greedy. | |
356 ;; *** ERROR: =over on line 1 without closing =back (at head1) at line 3 in file x.pod | |
357 ;; | |
358 "^\\*\\*\\* \\(?:ERROR\\|\\(WARNING\\)\\).* \\(?:at\\|on\\) line \ | |
359 \\([0-9]+\\) \\(?:.* \\)?in file \\([^ \t\n]+\\)" | |
360 3 2 nil (1)) | |
361 (compilation-perl--Test | |
362 ;; perl Test module error messages. | |
363 ;; Style per the ok() function "$context", eg. | |
364 ;; # Failed test 1 in foo.t at line 6 | |
365 ;; | |
366 "^# Failed test [0-9]+ in \\([^ \t\r\n]+\\) at line \\([0-9]+\\)" | |
367 1 2) | |
368 (compilation-perl--Test::Harness | |
369 ;; perl Test::Harness output, eg. | |
370 ;; NOK 1# Test 1 got: "1234" (t/foo.t at line 46) | |
371 ;; | |
372 ;; Test::Harness is slightly designed for tty output, since | |
373 ;; it prints CRs to overwrite progress messages, but if you | |
374 ;; run it in with M-x compile this pattern can at least step | |
375 ;; through the failures. | |
376 ;; | |
377 "^.*NOK.* \\([^ \t\r\n]+\\) at line \\([0-9]+\\)" | |
378 1 2) | |
379 (compilation-weblint | |
380 ;; The style comes from HTML::Lint::Error::as_string(), eg. | |
381 ;; index.html (13:1) Unknown element <fdjsk> | |
382 ;; | |
383 ;; The pattern only matches filenames without spaces, since that | |
384 ;; should be usual and should help reduce the chance of a false | |
385 ;; match of a message from some unrelated program. | |
386 ;; | |
387 ;; This message style is quite close to the "ibm" entry which is | |
388 ;; for IBM C, though that ibm bit doesn't put a space after the | |
389 ;; filename. | |
390 ;; | |
391 "^\\([^ \t\r\n(]+\\) (\\([0-9]+\\):\\([0-9]+\\)) " | |
392 1 2 3) | |
342 ) | 393 ) |
343 "Alist of values for `compilation-error-regexp-alist'.") | 394 "Alist of values for `compilation-error-regexp-alist'.") |
344 | 395 |
345 (defcustom compilation-error-regexp-alist | 396 (defcustom compilation-error-regexp-alist |
346 (mapcar 'car compilation-error-regexp-alist-alist) | 397 (mapcar 'car compilation-error-regexp-alist-alist) |