Hi Mark,
You asked me to verify on Windows too. Having updated to the latest and greatest of trunk, I see that I'm now able to run ABCL from a path with spaces in them, so far so good. However, you said we require spaces to be %-encoded in pathnames now. Or was that in [jar:]file: pathnames only?
Because, when I do (DIRECTORY #p"") from "D:\abcl\my docs", I see
(#P"D:/abcl/my docs/")
which is not a file: pathname, so it's to be expected?
Anyway, the immediate regression seems gone. I suppose I need to test much more, but it's getting too late for it. I'd appreciate some directions, if you have time.
Thanks!
Bye,
Erik.
On Sat, Nov 27, 2010 at 12:09 PM, Mark Evenson evenson@panix.com wrote:
After testing under Windows, I've committed my proposed solution to the URI escaping issues in pathnames to the trunk as [r13506][1]. If fellow developers could build and test the ABCL-TEST-LISP system on their respective systems, I would appreciate it.
From the commit message:
Fix problems with #\Space characters in JAR pathnames.
We now require that inputs to the PATHNAME routines that have the URI scheme "jar:file" or "file" properly encode themselves as URIs according to RFC2396. Mainly this means that #\Space and #? characters in such strings should be percent encoded (i.e. "jar:file:/path%20with%20/space/and%3fquestion-mark"). The corresponding namestring routines have been adjusted to output such URI encoded representations, although the underlying PATHNAME objects contain unescaped values. The routines for loading FASLs have been adjusted to URI encode their inputs as well.
The #+ character is no longer an escape for #\Space (this was a bug).
-- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
armedbear-devel mailing list armedbear-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel