From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: fortran@gcc.gnu.org, emacs-devel@gnu.org
Subject: Re: Emacs and GFortran
Date: Mon, 30 Oct 2006 09:15:14 -0500 [thread overview]
Message-ID: <jwvr6wp6gfr.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <Pine.OSF.4.21.0610301122450.28710-100000@ax0rm1.roma1.infn.it> (Angelo Graziosi's message of "Mon\, 30 Oct 2006 11\:32\:38 +0100 \(MET\)")
> I would ask if there is a way to integrate Emacs with GFortran so that in
> case of compiler error one can jump to the line wher the error is born.
> This works with G77, GCC and G++ but not with GFortran.
Does that mean that GFortran does not use the standard GNU error format?
That would be unfortunate (and may be better fixed on GFortran's side).
Could you show us some sample error/warning messages?
Stefan
next prev parent reply other threads:[~2006-10-30 14:15 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 10:32 Emacs and GFortran Angelo Graziosi
2006-10-30 14:15 ` Stefan Monnier [this message]
2006-10-30 15:27 ` Angelo Graziosi
2006-10-30 15:38 ` Stefan Monnier
2006-10-30 16:14 ` Steve Kargl
2006-10-30 18:28 ` Stefan Monnier
2006-10-30 20:35 ` Angelo Graziosi
2006-10-30 21:00 ` Tobias Burnus
2006-10-31 8:32 ` Angelo Graziosi
2006-10-31 10:54 ` Angelo Graziosi
2006-10-31 16:06 ` Stuart D. Herring
2006-10-31 23:24 ` Angelo Graziosi
2006-10-30 21:16 ` Nick Roberts
2006-10-30 19:16 ` Richard Stallman
2006-10-30 21:13 ` Steve Kargl
2006-10-31 4:02 ` Miles Bader
2006-10-31 4:31 ` Eli Zaretskii
2006-10-31 4:31 ` Steve Kargl
2006-10-31 22:07 ` Eli Zaretskii
2006-11-01 2:13 ` Richard Stallman
2006-11-01 2:16 ` Miles Bader
2006-10-31 6:11 ` Stefan Monnier
2006-10-31 6:43 ` FX Coudert
2006-11-01 2:14 ` Richard Stallman
2006-11-01 2:23 ` Miles Bader
2006-10-31 8:26 ` Angelo Graziosi
2006-10-31 15:10 ` Steve Kargl
2006-10-31 15:47 ` Angelo Graziosi
2006-10-31 16:00 ` Chong Yidong
2006-11-01 16:40 ` Richard Stallman
2006-11-01 17:37 ` Warren Turkal
2006-11-01 18:03 ` Steve Kargl
2006-11-01 20:37 ` Stefan Monnier
2006-11-01 20:39 ` Alfred M. Szmidt
2006-11-01 21:30 ` Steve Kargl
2006-11-01 21:51 ` Alfred M. Szmidt
2006-11-01 22:35 ` Steve Kargl
2006-11-01 22:49 ` Alfred M. Szmidt
2006-11-01 23:26 ` Steve Kargl
2006-11-01 23:35 ` Alfred M. Szmidt
2006-11-02 3:12 ` Steve Kargl
2006-11-03 2:40 ` Chong Yidong
2006-11-03 3:32 ` Steve Kargl
2006-11-03 10:05 ` David Kastrup
2006-11-03 2:44 ` Chong Yidong
2006-11-02 13:26 ` Alfred M. Szmidt
2006-11-02 19:00 ` Thomas Koenig
2006-11-02 20:22 ` Eli Zaretskii
2006-11-02 20:32 ` David Kastrup
2006-11-03 13:26 ` Eli Zaretskii
2006-11-02 20:38 ` Thomas Koenig
2006-11-02 20:43 ` Steve Kargl
2006-11-03 12:30 ` Eli Zaretskii
2006-11-03 12:58 ` David Kastrup
2006-11-03 13:40 ` Eli Zaretskii
2006-11-02 22:27 ` François-Xavier Coudert
2006-11-03 12:51 ` Eli Zaretskii
2006-11-03 0:43 ` Steven Bosscher
2006-11-03 1:08 ` Alfred M. Szmidt
2006-11-03 1:21 ` Steve Kargl
2006-11-03 2:32 ` Brooks Moses
2006-11-03 18:59 ` Nick Roberts
2006-11-03 20:27 ` Brooks Moses
2006-11-15 4:09 ` Brooks Moses
2006-11-15 4:30 ` Nick Roberts
2006-11-15 5:09 ` Brooks Moses
2006-11-15 7:57 ` Nick Roberts
2006-11-15 9:03 ` David Kastrup
2006-11-15 8:43 ` David Kastrup
2006-11-15 9:14 ` Andrew Pinski
2006-11-15 9:16 ` David Kastrup
2006-11-16 6:23 ` Richard Stallman
2006-11-03 7:06 ` Steven Bosscher
2006-11-03 13:10 ` Eli Zaretskii
2006-11-04 6:37 ` Richard Stallman
2006-11-03 13:05 ` Eli Zaretskii
2006-10-31 23:01 ` Eli Zaretskii
2006-11-02 22:20 ` Paul Thomas
2006-11-03 12:45 ` Eli Zaretskii
2006-11-03 13:14 ` David Kastrup
2006-11-03 13:42 ` Eli Zaretskii
[not found] <45462048.8020102@net-b.de>
[not found] ` <20061030161402.15694.qmail@web81209.mail.mud.yahoo.com>
2006-10-30 16:18 ` François-Xavier Coudert
2006-10-31 1:59 ` Miles Bader
2006-10-31 2:46 ` Steve Kargl
2006-10-31 3:49 ` Miles Bader
2006-10-31 4:23 ` Steve Kargl
2006-10-31 5:39 ` stephen
2006-10-31 16:40 ` Alfred M. Szmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvr6wp6gfr.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=fortran@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).