From: Alex Vong <alexvong1995@gmail.com>
To: swedebugia <swedebugia@riseup.net>
Cc: guile-user@gnu.org
Subject: Re: Cryptic error messages: Bug in guile?
Date: Tue, 13 Nov 2018 09:48:11 +0800 [thread overview]
Message-ID: <87o9atzr1g.fsf@gmail.com> (raw)
In-Reply-To: <ae70bbcf-6ecd-a537-93d5-bf912f7bf186@riseup.net> (swedebugia's message of "Tue, 13 Nov 2018 02:35:54 +0100")
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
Hello,
swedebugia <swedebugia@riseup.net> writes:
> Hi
>
> I try to package for guix.
> Sometimes I forget a parens somewhere.
>
> When I invoke make in the guix source tree the parens error will be
> reported as any other kind of error. (unbound variable, package not
> found, etc)
>
> I would like to know if there is a way to avoid/improve this.
>
> E.g. make guile count parens before evaluation or whatever so that I
> get a clear error, fast.
>
> Alternatively maybe somebody else has a parens counter script I could
> use? E.g. I could tell make to first traverse all files looking for
> unmatching parens.
What error message do you receive? Usually I get something like:
ERROR: In procedure read:
In procedure scm_i_lreadparen: #<unknown port>:1:2: end of file
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2018-11-13 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 1:35 Cryptic error messages: Bug in guile? swedebugia
2018-11-13 1:44 ` brettg
2018-11-13 1:48 ` Alex Vong [this message]
2018-11-20 20:47 ` 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=87o9atzr1g.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=guile-user@gnu.org \
--cc=swedebugia@riseup.net \
/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).