From: Kevin Ryde <user42@zip.com.au>
To: 3928@emacsbugs.donarmstrong.com
Subject: bug#3928: compilation-mode not matching perl and more [regression]
Date: Mon, 27 Jul 2009 11:13:07 +1000 [thread overview]
Message-ID: <871vo39bdo.fsf_-_@blah.blah> (raw)
In-Reply-To: <handler.3928.B.124852579914015.ack@emacsbugs.donarmstrong.com> (Emacs bug Tracking System's message of "Sat, 25 Jul 2009 12:50:04 +0000")
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
The ada entry is afflicted too (it's supposed to match the second part
of its compilation.txt, its first part is matched by the gnu pattern).
So,
2009-07-27 Kevin Ryde <user42@zip.com.au>
* progmodes/compile.el (compilation-error-regexp-alist-alist):
In ada, aix, ftnchek, mips-1, mips-2, perl, sun, 4bsd entries add ".*"
so as to match in the middle of a line, now that there's a "^" anchor
is again enforced by compilation-mode-font-lock-keywords. These
patterns were otherwise failing to match anything at all.
In the 4bsd entry remove the "^" from inside the \\(\\) grouping since
it's now unnecessary and since inside a group it isn't recognised by
the omake indentation hack in compilation-mode-font-lock-keywords
(meaning it wouldn't work with indentation).
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: compile.el.cope-with-anchoring-2.diff --]
[-- Type: text/x-diff, Size: 3370 bytes --]
*** compile.el 11 Jul 2009 07:12:48 +1000 1.495
--- compile.el 26 Jul 2009 14:43:04 +1000
***************
*** 170,179 ****
of[ \t]+\"?\\([a-zA-Z]?:?[^\":\n]+\\)\"?:" 3 2 nil (1))
(ada
! "\\(warning: .*\\)? at \\([^ \n]+\\):\\([0-9]+\\)$" 2 3 nil (1))
(aix
! " in line \\([0-9]+\\) of file \\([^ \n]+[^. \n]\\)\\.? " 2 1)
(ant
"^[ \t]*\\[[^] \n]+\\][ \t]*\\([^: \n]+\\):\\([0-9]+\\):\\(?:\\([0-9]+\\):[0-9]+:[0-9]+:\\)?\
--- 170,179 ----
of[ \t]+\"?\\([a-zA-Z]?:?[^\":\n]+\\)\"?:" 3 2 nil (1))
(ada
! "\\(warning:\\)?.* at \\([^ \n]+\\):\\([0-9]+\\)$" 2 3 nil (1))
(aix
! ".* in line \\([0-9]+\\) of file \\([^ \n]+[^. \n]\\)\\.? " 2 1)
(ant
"^[ \t]*\\[[^] \n]+\\][ \t]*\\([^: \n]+\\):\\([0-9]+\\):\\(?:\\([0-9]+\\):[0-9]+:[0-9]+:\\)?\
***************
*** 207,213 ****
"^Error [0-9]+ at (\\([0-9]+\\):\\([^)\n]+\\))" 2 1)
(ftnchek
! "\\(^Warning .*\\)? line[ \n]\\([0-9]+\\)[ \n]\\(?:col \\([0-9]+\\)[ \n]\\)?file \\([^ :;\n]+\\)"
4 2 3 (1))
(iar
--- 207,213 ----
"^Error [0-9]+ at (\\([0-9]+\\):\\([^)\n]+\\))" 2 1)
(ftnchek
! "\\(Warning\\)?.* line[ \n]\\([0-9]+\\)[ \n]\\(?:col \\([0-9]+\\)[ \n]\\)?file \\([^ :;\n]+\\)"
4 2 3 (1))
(iar
***************
*** 284,292 ****
;; Should be lint-1, lint-2 (SysV lint)
(mips-1
! " (\\([0-9]+\\)) in \\([^ \n]+\\)" 2 1)
(mips-2
! " in \\([^()\n ]+\\)(\\([0-9]+\\))$" 1 2)
(msft
;; AFAWK, The message may be a "warning", "error", or "fatal error".
--- 284,292 ----
;; Should be lint-1, lint-2 (SysV lint)
(mips-1
! ".* (\\([0-9]+\\)) in \\([^ \n]+\\)" 2 1)
(mips-2
! ".* in \\([^()\n ]+\\)(\\([0-9]+\\))$" 1 2)
(msft
;; AFAWK, The message may be a "warning", "error", or "fatal error".
***************
*** 308,314 ****
;; warnings" in recent perl when breaking circular references
;; during program or thread exit.
(perl
! " at \\([^ \n]+\\) line \\([0-9]+\\)\\(?:[,.]\\|$\\| \
during global destruction\\.$\\)" 1 2)
(php
--- 308,314 ----
;; warnings" in recent perl when breaking circular references
;; during program or thread exit.
(perl
! "XXXXXXXXXX.* at \\([^ \n]+\\) line \\([0-9]+\\)\\(?:[,.]\\|$\\| \
during global destruction\\.$\\)" 1 2)
(php
***************
*** 332,338 ****
nil 1 nil (3) nil (2 (compilation-face '(3))))
(sun
! ": \\(?:ERROR\\|WARNIN\\(G\\)\\|REMAR\\(K\\)\\) \\(?:[[:alnum:] ]+, \\)?\
File = \\(.+\\), Line = \\([0-9]+\\)\\(?:, Column = \\([0-9]+\\)\\)?"
3 4 5 (1 . 2))
--- 332,338 ----
nil 1 nil (3) nil (2 (compilation-face '(3))))
(sun
! ".*: \\(?:ERROR\\|WARNIN\\(G\\)\\|REMAR\\(K\\)\\) \\(?:[[:alnum:] ]+, \\)?\
File = \\(.+\\), Line = \\([0-9]+\\)\\(?:, Column = \\([0-9]+\\)\\)?"
3 4 5 (1 . 2))
***************
*** 345,351 ****
1 2 nil (4))
(4bsd
! "\\(?:^\\|:: \\|\\S ( \\)\\(/[^ \n\t()]+\\)(\\([0-9]+\\))\
\\(?:: \\(warning:\\)?\\|$\\| ),\\)" 1 2 nil (3))
(gcov-file
--- 345,351 ----
1 2 nil (4))
(4bsd
! "^\\(?:\\|.*:: \\|.*\\S ( \\)\\(/[^ \n\t()]+\\)(\\([0-9]+\\))\
\\(?:: \\(warning:\\)?\\|$\\| ),\\)" 1 2 nil (3))
(gcov-file
next prev parent reply other threads:[~2009-07-27 1:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <uy8wfgt10x.fsf_-_@fencepost.gnu.org>
2009-07-25 12:42 ` bug#3928: 23.1.50; compilation-mode not matching perl and more [regression] Kevin Ryde
[not found] ` <handler.3928.B.124852579914015.ack@emacsbugs.donarmstrong.com>
2009-07-27 1:13 ` Kevin Ryde [this message]
2009-10-13 3:45 ` bug#3928: marked as done (23.1.50; compilation-mode not matching perl and more [regression]) Emacs bug Tracking System
2009-10-09 13:40 ` bug#4689: 23.1.50; Matching of error lines in *compilation* buffer is broken for perl-files LanX
2009-10-09 16:04 ` Glenn Morris
2009-10-09 16:28 ` LanX
2009-10-12 7:51 ` Heddy Boubaker
2009-10-12 14:26 ` LanX
2009-10-12 16:24 ` Glenn Morris
2009-10-12 16:30 ` Processed: " Emacs bug Tracking System
2009-10-12 19:36 ` Glenn Morris
2009-10-12 22:04 ` LanX
2009-10-12 16:57 ` Juanma Barranquero
2009-10-09 16:39 ` Glenn Morris
2009-10-09 16:46 ` LanX
2009-10-09 18:29 ` Glenn Morris
2009-10-09 20:28 ` LanX
2009-10-09 21:24 ` Glenn Morris
2009-10-10 14:49 ` Jason Rumney
2009-10-13 3:45 ` bug#4689: marked as done (23.1.50; Matching of error lines in *compilation* buffer is broken for perl-files) Emacs bug Tracking System
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871vo39bdo.fsf_-_@blah.blah \
--to=user42@zip.com.au \
--cc=3928@emacsbugs.donarmstrong.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.