From: Jose Antonio Ortega Ruiz <INVALID.NOREPLY@gnu.org>
To: Jose Antonio Ortega Ruiz <jao@gnu.org>, bug-guile@gnu.org
Subject: [bug #30903] Error line numbers are wrong
Date: Mon, 30 Aug 2010 02:13:39 +0000 [thread overview]
Message-ID: <20100830-021338.sv424.69189@savannah.gnu.org> (raw)
In-Reply-To: <20100830-020856.sv424.31665@savannah.gnu.org>
Follow-up Comment #1, bug #30903 (project guile):
Sorry, pasted the wrong error trace. Here's the real one:
;;; compiling foo.scm
;;; compiled
/home/jao/.cache/guile/ccache/2.0-0.R-LE-4/home/jao/tmp/foo.scm.go
foo.scm:3:1: In procedure module-lookup:
foo.scm:3:1: Unbound variable: a
i.e., line 3 instead of line 5.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30903>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2010-08-30 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 2:08 [bug #30903] Error line numbers are wrong Jose Antonio Ortega Ruiz
2010-08-30 2:13 ` Jose Antonio Ortega Ruiz [this message]
2011-02-02 19:47 ` Andy Wingo
2011-10-22 14:23 ` bug#9837: " Ludovic Courtès
2011-10-22 15:59 ` Ludovic Courtès
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100830-021338.sv424.69189@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=jao@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.
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).