From: Paul Emsley <emsley@ysbl.york.ac.uk>
Subject: guile and XML (mixp)
Date: Wed, 22 Nov 2006 17:26:42 +0000 [thread overview]
Message-ID: <1164216402.3464.33.camel@localhost.localdomain> (raw)
Anyone using mixp and can help out here?
$ [configure/make/make install all clean]
$ cd test
$ guile-expat test-mixp.scm
/xxx/guile/1.6/ice-9/syncase.scm:130:16: In procedure scm-error in expression (scm-error (quote misc-error) who ...):
/xxx/share/guile/1.6/ice-9/syncase.scm:130:16: invalid syntax ()
$ guile --version
Guile 1.6.7
using mixp-0.4
Cheers,
Paul.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2006-11-22 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 17:26 Paul Emsley [this message]
2006-11-22 18:51 ` guile and XML (mixp) Neil Jerram
2006-11-27 13:30 ` Jon Wilson
[not found] ` <456AE847.5030101@fastmail.fm>
2006-11-27 22:05 ` Neil Jerram
2006-11-27 22:44 ` Jon Wilson
2006-11-28 8:43 ` Ludovic Courtès
2006-11-28 13:36 ` Dale P. Smith
-- strict thread matches above, loose matches on Subject: below --
2006-11-22 20:56 dsmich
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=1164216402.3464.33.camel@localhost.localdomain \
--to=emsley@ysbl.york.ac.uk \
/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).