Hi

I've sent a bugreport:

4689: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=4689 Emacs Bug Tracking System

Here a workaround patch I found to make the regex match again:

Changing in mode-compile.el from

------------------------------------------------

(defvar perl-compilation-error-regexp-alist
  ;; Contributed by Martin Jost
  '(
    ;; PERL 4
    ("in file \\([^ ]+\\) at line \\([0-9]+\\).*" 1 2)
    ;; PERL 5   Blubber at FILE line XY, <XY> line ab.
    ("at \\([^ ]+\\) line \\([0-9]+\\)," 1 2)
    ;; PERL 5   Blubber at FILE line XY.
    ("at \\([^ ]+\\) line \\([0-9]+\\)." 1 2)
    )
  ;; This look like a paranoiac regexp: could anybody find a better
one? (which WORK).
  ;;'(("^[^\n]* \\(file\\|at\\) \\([^ \t\n]+\\) [^\n]*line \\([0-9]+\\
+)
[\\.,]" 2 3))
  "Alist that specifies how to match errors in perl output.
 
See variable compilation-error-regexp-alist for more details.")

[download]

------------------------------------------------

to

------------------------------------------------

(defvar perl-compilation-error-regexp-alist
  ;; Contributed by Martin Jost
  '(
    ;; PERL 4
    ("^[^\n]* in file \\([^ ]+\\) at line \\([0-9]+\\).*" 1 2)
    ;; PERL 5   Blubber at FILE line XY, <XY> line ab.
    ("^[^\n]* at \\([^ ]+\\) line \\([0-9]+\\)," 1 2)
    ;; PERL 5   Blubber at FILE line XY.
    ("^[^\n]* at \\([^ ]+\\) line \\([0-9]+\\)." 1 2)
    )
  ;; This look like a paranoiac regexp: could anybody find a better
one? (which WORK).
  ;;'(("^[^\n]* \\(file\\|at\\) \\([^ \t\n]+\\) [^\n]*line \\([0-9]+\\
+)
[\\.,]" 2 3))
  "Alist that specifies how to match errors in perl output.
 
See variable compilation-error-regexp-alist for more details.")

[download]
------------------------------------------------

fixes the problem in emacs 23! 8)

(Plz note: the WHOLE error line gets underlined now)

Cheers Rolf

UPDATE: The former patch only works for perl-mode. This is a patch for cperl-mode.el Version 6.2

 (defvar cperl-compilation-error-regexp-alist-lanx-patch
  '(
    ;; PERL 4
    ("^[^\n]* in file \\([^ ]+\\) at line \\([0-9]+\\).*" 1 2)
    ;; PERL 5   Blubber at FILE line XY, <XY> line ab.
    ("^[^\n]* at \\([^ ]+\\) line \\([0-9]+\\)," 1 2)
    ;; PERL 5   Blubber at FILE line XY.
    ("^[^\n]* at \\([^ ]+\\) line \\([0-9]+\\)." 1 2)
    )
  "Alist that specifies how to match errors in perl output.")
 
(if (fboundp 'eval-after-load)
    (eval-after-load
    "mode-compile"
      '(setq perl-compilation-error-regexp-alist
         cperl-compilation-error-regexp-alist-lanx-patch)))

[download]

In reply to Re: [emacs23] Upgrading with cperl-mode and mode-compile (Workaround +Ticket) by LanX
in thread [emacs23] Upgrading with cperl-mode and mode-compile by LanX

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.