Andy Wingo skribis:
> On Sun 16 Dec 2012 21:31, Mark H Weaver writes:
>
>> Also, since your script contains non-ASCII characters, you should place
>> a coding declaration in the file so that Guile will know what encoding
>> to use when reading it. If your script is in UTF-8, then put this in
>>
Andy Wingo writes:
> On Sun 16 Dec 2012 21:31, Mark H Weaver writes:
>
>> Also, since your script contains non-ASCII characters, you should place
>> a coding declaration in the file so that Guile will know what encoding
>> to use when reading it. If your script is in UTF-8, then put this in
>>
Hi,
I'm catching up with mail and thought you might be interested in my
thoughts. They're just my thoughts, the thoughts of one Guile hacker,
and I don't represent Guile with them -- so please do make up your own
minds.
I basically agree with Ludo and Mark that proprietary, centralized
social ne
On Sun 16 Dec 2012 21:31, Mark H Weaver writes:
> Also, since your script contains non-ASCII characters, you should place
> a coding declaration in the file so that Guile will know what encoding
> to use when reading it. If your script is in UTF-8, then put this in
> the first 500 characters of
On Wed 05 Dec 2012 03:43, Nala Ginrut writes:
> You may post a trace result like that:
> ===cut=
> ,tr (use-modules (ice-9 colorized))
> ===end=
FWIW this probably doesn't do what you want -- the use-modules form is
actually evaluated twice
On Mon 03 Dec 2012 16:09, Thien-Thi Nguyen writes:
> BTW, ‘a2ixin foo.sxml’ works fine under Guile 2.
> Getting the .sxml in the first place is the problem, there.
IIRC the problem here was entities like ©right; not being defined?
For that you can use:
-- Function: define-parsed-entity! en
