Nick Roberts wrote:
Bob McIsaac writes:
> The compilation-error-regexp works for gcc output but not for
> Openwatcom. However, it worked fine for emacs-21. It seems the regexp
This isn't really my area but it's such a concise bug report it deserves a
reply. I've checked the changes below into the trunk. Can you please confirm
that they work for you? In particular, when the filename is absolute, e.g.,
c:\src\ctrl\lister.c(109): ....
Hi:
Two thumbs up for the quality of help provided by free software people.
I already received a .emacs patch that works. I can also test your
(Nick's) solution but I need some hint as to how. Here is the
.emacs one.
-bob-
==================================
Chong Yidong wrote:
The compilation-error-regexp works for gcc output but not for
Openwatcom. However, it worked fine for emacs-21. It seems the regexp no
longer accepts parentheses around the line number.
----- gcc example is ok ----
-*- mode: compilation; default-directory: "c:/altm/acp-7-3/build/" -*-
../src/vi/vi_main.c:53: `xint' undeclared (first use in this function)
../src/vi/vi_main.c:53: (Each undeclared identifier is reported only once
------- Open Watcom Make Version 1.7 -- not ok because of line number ======
..\src\ctrl\lister.c(109): Error! E1009: Expecting ';' but found '{'
..\src\ctrl\lister.c(120): Warning! W201: Unreachable code
I don't have Openwatcom installed, so I can't test the fix directly.
Could you help me with testing?
Please add the following code to your .emacs, then try compiling. Does
compilation now work for both gcc and openwatcom? If possible, please
test with any other back-end to M-x compile that you have available, to
ensure that nothing else broke.
Thanks.
(require 'compile)
(push '(openwatcom
"^\\([0-9]*[^0-9\n]\\(?:[^\n ]\\| [^-/\n]\\)*?\\)(\\([0-9]+\\)): ?\
\\(?:\\(Warning! ?W[0-9]+:\\)\\|\\(Error! ?E[0-9]+:\\)\\|\\(.\\)\\)"
1 2 nil (3 . 5))
compilation-error-regexp-alist-alist)
(push 'openwatcom compilation-error-regexp-alist)
Hi:
I am pleased to report that your patch works with gcc, openwatcom,
grep, and Doxygen!
Thanks for the timely solution.
-Bob-
|