This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: Emacs and GFortran
- From: Angelo Graziosi <Angelo dot Graziosi at roma1 dot infn dot it>
- To: Tobias Burnus <burnus at net-b dot de>
- Cc: fortran at gcc dot gnu dot org, emacs-devel at gnu dot org
- Date: Tue, 31 Oct 2006 11:54:48 +0100 (MET)
- Subject: Re: Emacs and GFortran
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
>