Re: Emacs and GFortran

[Angelo Graziosi]

It seems that changing :

(eval-after-load "compile"
   '(setq compilation-error-regexp-alist
       (cons '("^In file \\(.+\\):\\([0-9]+\\)" 1 2)
          compilation-error-regexp-alist)))


with


(eval-after-load "compile"
   '(setq compilation-error-regexp-alist
       (cons '("^\\(?:In\\| In\\) file \\(.+\\):\\([0-9]+\\)" 1 2)
          compilation-error-regexp-alist)))


in .emacs, works both for GFortran that G95. Do you confirm ?


In any case this should be considered only a workaround. the best solution
being that each compiler conforms itself to a common standard like G77.


Cheers,

   Angelo.




On Mon, 30 Oct 2006, Tobias Burnus wrote:

> Hi,
> 
> Angelo Graziosi wrote:
> >> By the way, g95 has the same problem.
> >>     
> >
> > Adding
> >
> > (eval-after-load "compile"
> >    '(setq compilation-error-regexp-alist
> >        (cons '("^In file \\(.+\\):\\([0-9]+\\)" 1 2)
> >           compilation-error-regexp-alist)))
> >
> > in .emacs solves it.
> >
> >
> > So, is there something similar for GFortran ?
> >   
> Doesn't this work for gfortran? I think the output is the same:
> "In file <filename>:<line>".
> Thus it should work with both compilers. (It probably predates the
> g95-gfortran split.)
> 
> Tobias
>