() Ian Price
() Sun, 06 Nov 2011 21:04:31 +
If you use the web modules, _please_ comment on my suggestions for
chunked encoding support. See
I don't use those modules (yet?), but i did notice something:
+ (extension-start (string-index str (lambda (c) (or (char=? c #\;)
Hello,
> My question is that the command line arguments seems to be parsed
> ... ... or can anybody tell me how to read arguments correctly?
You must also set port encoding, see manual section 6.14.1 for details:
(set-port-encoding! (current-output-port) "utf-8")
Cheers,
David
On Mon, Nov 7, 2011 at 6:59 AM, David Pirotte wrote:
> You must also set port encoding, see manual section 6.14.1 for details:
>
> (set-port-encoding! (current-output-port) "utf-8")
>
Thanks for responding.
But after a setlocale, utf-8 output is already fine. The problem is
argument pars
On Mon, Nov 7, 2011 at 11:31 PM, cong gu wrote:
> On Mon, Nov 7, 2011 at 6:59 AM, David Pirotte wrote:
> > You must also set port encoding, see manual section 6.14.1 for details:
> >
> >(set-port-encoding! (current-output-port) "utf-8")
> >
>
> Thanks for responding.
>
> But after a setl
() cong gu
() Mon, 7 Nov 2011 09:31:49 -0600
After I add a setlocale to boot-9.scm, all things works.
But is there a "normal" way to fix this?
Besides boot-9.scm, guile also runs init.scm (in ‘%load-path’).
Perhaps you can experiment with calling ‘setlocale’ there.
On Tue, Nov 8, 2011 at 3:16 AM, Thien-Thi Nguyen wrote:
> () cong gu
> () Mon, 7 Nov 2011 09:31:49 -0600
>
> After I add a setlocale to boot-9.scm, all things works.
> But is there a "normal" way to fix this?
>
> Besides boot-9.scm, guile also runs init.scm (in ‘%load-path’).
> Perhaps you c
