You're confused because URL:ENCODE-STRING has nothing to do with "url
encoding", which the encoding used for
application/x-www-form-urlencoded (and which itself has nothing to do
with URIs).
As the code comment says, this is just a backwards compatibility
procedure for something that existed in th
> From:
> Date: Wed, 02 May 2012 13:21:32 +0200
>
> Hello fellow Schemers!
>
> I may misunderstand things here, but isn't URL:ENCODE-STRING meant to
> properly encode characters that are special to urls?
It was meant to "encode query string", not "encode arbitrary text"?
> [...] I'm trying to
Date: Wed, 02 May 2012 09:28:31 +0200
From:
Yesterday I've tried to get current SLIME (2012-03-06 here) to work with
MIT/GNU Scheme, and fixed a few things. Find attached my patches. How
should I best prepare them so they get a chance at getting accepted into
GIT?
It looks like
Date: Wed, 02 May 2012 13:21:32 +0200
From:
I may misunderstand things here, but isn't URL:ENCODE-STRING meant to
propertly encode characters that are special to urls? Examples would be
=, & and ; (which should all be encoded). However,
> (url:encode-string "a=b&b=c;c=d")
Hello fellow Schemers!
I may misunderstand things here, but isn't URL:ENCODE-STRING meant to
propertly encode characters that are special to urls? Examples would be
=, & and ; (which should all be encoded). However,
> (url:encode-string "a=b&b=c;c=d")
just echoes that string literally ("a=b&b=
I get bounces from naver.com for netscou...@naver.com in Korean. Google
translate indicates that this e-mail has blocked mail from the list
address. Would it be possible to remove the recipient from the list, in
order to avoid the bounces?
Greetings,
Peter
--- Begin Message ---
NAVER - http://ww
Found another typo in the description of signal-condition.
Greetings,
Peter
From 61bb14a32a8183645b73eefdbe90da32966ac64a Mon Sep 17 00:00:00 2001
From: Peter Feigl
Date: Wed, 2 May 2012 09:30:36 +0200
Subject: [PATCH] fixing typo: duplicated word "creates"
---
doc/ref-manual/error.texi |2
Hello fellow Schemers!
Yesterday I've tried to get current SLIME (2012-03-06 here) to work with
MIT/GNU Scheme, and fixed a few things. Find attached my patches. How
should I best prepare them so they get a chance at getting accepted into
GIT?
Greetings,
Peter
From 203f5ab2624f366b41b0dcd144f1fa
