4:41 p.m.
When compiling Fortran code using gfortran inside xemacs I cannot get
xemacs to point to the source lines for errors and warnings. I have
attempted to get help on comp.emacs.xemacs but no luck yet. I will also
try the gfortran mailing list.
Thanks.
-Tom
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:58 a.m.
Tom Browder writes:
When compiling Fortran code using gfortran inside xemacs I cannot
get xemacs to point to the source lines for errors and warnings
just an unverified suggestion: try with f90.el
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
12:31 p.m.
On Sun, Jan 18, 2009 at 12:58 AM, Giacomo Boffi <giacomo.boffi(a)polimi.it> wrote:
Tom Browder writes:
> When compiling Fortran code using gfortran inside xemacs I cannot
> get xemacs to point to the source lines for errors and warnings
just an unverified suggestion: try with f90.el
Thanks, but it doesn't help--it shows the same behavior as with
fortran.el (see details in my msg to Matt).
-Tom
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
12:30 p.m.
On Sun, Jan 18, 2009 at 6:31 AM, Tom Browder <tom.browder(a)gmail.com> wrote:
On Sun, Jan 18, 2009 at 12:58 AM, Giacomo Boffi
<giacomo.boffi(a)polimi.it> wrote:
> Tom Browder writes:
> > When compiling Fortran code using gfortran inside xemacs I cannot
> > get xemacs to point to the source lines for errors and warnings
I just looked at compile.el in xemacs-packages/lisp/base (xemacs 21.4)
and I don't think it is set up to handle the warning and error format
of gfortran as near as I can tell. I will look at the emacs version
and see if I can see a difference since emacs has been reported to
work with gformat.
-Tom
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
3:53 p.m.
On Mon, Jan 19, 2009 at 6:30 AM, Tom Browder <tom.browder(a)gmail.com> wrote:
...
I just looked at compile.el in xemacs-packages/lisp/base (xemacs
21.4)
and I don't think it is set up to handle the warning and error format
of gfortran as near as I can tell. I will look at the emacs version
and see if I can see a difference since emacs has been reported to
work with gformat.
Well, the two files differ considerably--looks like they have diverged
since about 1995. The regexes for gnu compilers are significantly
more complex in the emacs case--maybe handling for gfortran is buried
in there somewhere.
And I confirmed that emacs handles gfortran output fine.
Is anyone maintaining compile.el for xemacs now?
I also found mode-compile.el and tried to get it to autoload but
haven't had any success. I also tried xemacs 21.5.b28 and couldn't
get compile to work at all.
Suggestions welcome.
Thanks.
-Tom
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
2:29 a.m.
Hi there,
--- On Mon, 1/19/09, Tom Browder <tom.browder(a)gmail.com> wrote:
From: Tom Browder <tom.browder(a)gmail.com>
Subject: Re: Fortran.el
To: giacomo.boffi(a)polimi.it
Cc: xemacs-beta(a)xemacs.org
Date: Monday, January 19, 2009, 11:53 PM
On Mon, Jan 19, 2009 at 6:30 AM, Tom Browder
<tom.browder(a)gmail.com> wrote:
...
> I just looked at compile.el in
xemacs-packages/lisp/base (xemacs 21.4)
> and I don't think it is set up to handle the
warning and error format
> of gfortran as near as I can tell. I will look at the
emacs version
> and see if I can see a difference since emacs has been
reported to
> work with gformat.
Well, the two files differ considerably--looks like they
have diverged
since about 1995. The regexes for gnu compilers are
significantly
more complex in the emacs case--maybe handling for gfortran
is buried
in there somewhere.
The current version of compile.el is also causing some functions of eshell-mode producing
warning message. I am really want to sync it up with emacs latest GPL v2 version, but
I'd have no time these days...
And I confirmed that emacs handles gfortran output fine.
It seemed that compile.el in GNU Emacs 21.x was almost identical to XEmacs' one, but
was rewrote in GNU Emacs 22.x
Is anyone maintaining compile.el for xemacs now?
I also found mode-compile.el and tried to get it to
autoload but
haven't had any success. I also tried xemacs 21.5.b28
and couldn't
get compile to work at all.
Suggestions welcome.
Thanks.
-Tom
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
3:15 a.m.
On Mon, Jan 19, 2009 at 8:29 PM, It's me FKtPp ;) <fktpp(a)xemacs.org> wrote:
Hi there,
...
The current version of compile.el is also causing some functions of
eshell-mode producing warning message. I am really want to sync it up with emacs latest
GPL v2 version, but I'd have no time these days...
...
It seemed that compile.el in GNU Emacs 21.x was almost identical to
XEmacs' one, but was rewrote in GNU Emacs 22.x
...
Thanks for the information. Tomorrow I'm going to try to modify the
existing regexes in compile.el to see if I can get changed behavior.
-Tom
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
12:06 a.m.
Ar an fichiú lá de mí Eanair, scríobh It's me FKtPp ;\):
The current version of compile.el is also causing some functions of
eshell-mode producing warning message. I am really want to sync it up
with emacs latest GPL v2 version, but I'd have no time these days...
Good for you that you have a job that’s busy! Lots of people don’t.
Jerry James attempted syncing compile.el in 2007 or so, if I remember things
correctly, and he reverted his changes, there were subtle bugs that he
couldn’t easily fix. It’s probably worth talking to him about such a sync,
unless the version that he was trying to sync is much older than the one
you’re interested in.
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghe, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
10:16 a.m.
>>>> Tom wrote:
Tom> When compiling Fortran code using gfortran inside xemacs I cannot get
Tom> xemacs to point to the source lines for errors and warnings.
OK. So you compile and get errors and warnings in the *compilation*
buffer. You then use M-x next-error or equivalent but xemacs doesn't
see any errors/warnings?
If that is the case then my guess is that gfortran outputs warning and
error messages that is not recognised by the regexps in the
compilation-error-regexp-alist and a new regexp for gfortran needs to
be designed.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
12:28 p.m.
On Sun, Jan 18, 2009 at 4:16 AM, Mats Lidell <matsl(a)xemacs.org> wrote:
>>>>> Tom wrote:
Tom> When compiling Fortran code using gfortran inside xemacs I cannot get
Tom> xemacs to point to the source lines for errors and warnings.
OK. So you compile and get errors and warnings in the *compilation*
buffer. You then use M-x next-error or equivalent but xemacs doesn't
see any errors/warnings?
No, it recognizes the warnings and errors but cannot find the source
(i.e., the main window doesn't show the offending source file).
Here's an example of the message in the mini-buffer after a select C-x
`:
Find this error in: (default argument list at ) /usr/local/src/
Note the same message appears when using g95 but, after the C-x `, the
main window shows the source buffer for the file with the first waring
or error and the cursor is on the offending line.
-Tom
P.S. And I'll try Giacomo's suggestion to use f90.el instead of gfortran.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:41 a.m.
>>>> 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.
Tom> Note the same message appears when using g95 but, after the C-x
Tom> `, the main window shows the source buffer for the file with the
Tom> first waring or error and the cursor is on the offending line.
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.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
5560
days inactive
5576
days old
10 comments
5 participants
participants (5)
-
Aidan Kehoe -
Giacomo Boffi -
It's me FKtPp ;) -
The XEmacs Package Smoketest -
Tom Browder