Steel Bank Common Lisp

Robert Uhl <eadmund42@...> writes:

> The reason for this is that one of my directories or files uses the ae
> ligature in its name.  

How is that ae ligature identified?  What is its encoding, and how do
you (or the kernel) know?

> This is on SBCL 0.9.6.  Any workarounds?

The short answer is no.

Disabling :sb-unicode might help, because without it it's a little
less strict about what is a base-char.  Aside from that, I believe
that someone else on these lists has patched their system to implement
*pathname-external-format*, which might be coerced into doing what you
want, and is probably closest to a good solution that I know of, but
nevertheless is quite sucky.  If you do find a patch, I'd be
interested to see it (and hear reasoning if it's generally
applicable).

Cheers,

Christophe

Christophe Rhodes <csr21@...> writes:
>
>> The reason for this is that one of my directories or files uses the
>> ae ligature in its name.
>
> How is that ae ligature identified?  What is its encoding, and how do
> you (or the kernel) know?

I'm going to guess that it's Unicode or iso-8859-1, given that my locale
is en_GB.UTF-8 and that this is a Linux box.

It doesn't matter atm, since that particular directory is actually
outside of the tree I should have been looking at; neglected to end a
directory path with '/' again...

-- 
Robert Uhl <http://public.xdi.org/=ruhl>
Ubi non accusator, ibi non judex.