On Tue, Jan 20, 2009 at 12:41 AM, Mats Lidell <matsl(a)xemacs.org> wrote:
>>>>> Tom Browder <tom.browder(a)gmail.com>
writes:
Tom> No, it recognizes the warnings and errors but cannot find the source
Tom> (i.e., the main window doesn't show the offending source file).
Well the errors and warnings are seen, of found, in the *compilation*
buffer by the use of regular expressions. The offending file and line
number is found by regexp matching. So if the regexps doesn't match
any error or warning in *compilation* the main window can't position
on the line of error.
...
Is the error or warning message exactly the same for both compilers?
Sometimes there are options to the compiler to control the formatting
of the warning and error messages. In that case maybe there is an
alternative format that works with the existing regexps.
Well, Mats, this morning I found on thewww.g95 site this HowTo:
http://www.g95.org/howto.shtml#emacs
By using it as a start at the end of my init.el file, I got this
combination to work (so far it does the trick):
;; TB: hack for gfortran (based on
http://www.g95.org/howto.shtml#emacs by
;; Helge Avlesen
;; typical error after compilation line: 'fmt_test.f:196.6:'
(eval-after-load "compile"
'(setq compilation-error-regexp-alist
(cons '("^\\(.+\\):\\([0-9]+\\)\.\\([0-9]+\\):" 1 2)
compilation-error-regexp-alist)))
Thanks, all.
Regards,
-Tom
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta