When guile 2.0 is used to write scripts, one have to manually do a
setlocale at the beginning of the script to enable non-asciiI
character support (why not by default?).
My question is that the command line arguments seems to be parsed
before any code in the script is executed (including the setlo
"R. P. Dillon" writes:
> (http-get (string->uri "http://www.cnn.com";))
>
> yields:
>
> web/client.scm:109:4: In procedure http-get:
> web/client.scm:109:4: Throw to key `bad-response' with args `("EOF while
> reading response body: ~a bytes of ~a" (18576 106274))'.
>
> In web/client.scm:
> 1
Hi all,
In LilyPond initialization code, at the moment we build a list of
scheme files to load from our %load-path and interpret as we go.
I'm currently hacking some code so that if we do the load-from-path
successfully we then call
(compile-file (%search-load-path "blah.scm") /blah.go).
However
Thanks for your response, Ian. I don't know how I missed the (web client)
module, but it's right there in my info page.
I've been experimenting with it, but am having similar problem to those
outlined below. I'm going to start reading some of the code, but my
initial impression is that there's l
"R. P. Dillon" writes:
> I'm currently working on a project to gather RSS data using Guile. I've been
I've done that. I highly recommend sxpath for this job.
> working with both the stable 2.0.3 version and the latest git repository. I'm
> fairly new to Guile, though, so I might be approaching
