GNU bug report logs -
#3928
23.1.50; compilation-mode not matching perl and more [regression]
Previous Next
Reported by: Kevin Ryde <user42 <at> zip.com.au>
Date: Sat, 25 Jul 2009 12:50:04 UTC
Severity: normal
Merged with 4689
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Mon, 12 Oct 2009 23:39:58 -0400
with message-id <uy8wfgt10x.fsf_-_ <at> fencepost.gnu.org>
and subject line Re: Bug#3928
has caused the Emacs bug report #3928,
regarding 23.1.50; compilation-mode not matching perl and more [regression]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact help-debbugs <at> gnu.org
immediately.)
--
3928: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3928
Emacs Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
[Message part 3 (text/plain, inline)]
Running "emacs -Q etc/compilation.txt" and scrolling down to the perl
section shows none of the sample perl errors matched at all, where I
hoped they would be.
I think the "^" anchor added by compilation-mode-font-lock-keywords
means perl and some other more obscure patterns need a ".*", like they
had back in Emacs 21, to work in the middle of a line.
I noticed this on the perl one. I thought it was working fine not so
long ago, so I don't know what/when/how it went bad. (The looseness of
Emacs 22 not anchoring reverted, but the patterns not put back at the
same time too??)
2009-07-25 Kevin Ryde <user42 <at> zip.com.au>
* progmodes/compile.el (compilation-error-regexp-alist-alist):
In 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).
[compile.el.cope-with-anchoring.diff (text/x-diff, attachment)]
[Message part 5 (text/plain, inline)]
In GNU Emacs 23.1.50.4 (i586-pc-linux-gnu, GTK+ Version 2.16.4)
of 2009-07-24 on blah.blah
configured using `configure 'CFLAGS=-O -g' '--prefix=/down/emacs/b/inst' '--with-x-toolkit=gtk''
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_AU
value of $XMODIFIERS: nil
locale-coding-system: iso-latin-1-unix
default-enable-multibyte-characters: t
[Message part 6 (message/rfc822, inline)]
Fixed by this change:
2009-10-12 Sam Steingold <sds at gnu.org>
* progmodes/compile.el (compilation-mode-font-lock-keywords): Do not
prepend "^ *" to non-anchored patterns, like the perl one (bug#3928).
This bug report was last modified 15 years and 228 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.