Scribit Andreas Krüger dies 24/09/2007 hora 09:31:
I think I know what causes your problem: it is caused by having a file in your home directory with a name that cannot be encoded with the locale you're trying to use. Bingo! That was the ticket!
Not so sure it's a bug in clisp, though. I have a bunch of files with names encoded in ISO-8859-15 and I copied one in my $HOME with an accentuated character, then invoked clisp while having fr_FR.UTF-8 as my locale (where the byte encoding of the previously mentioned character is not a legal one). clisp started fine. And as I previously explained Andreas, I could reproduce it's bug by using a locale not installed on the system. I would consider it a rather major bug if clisp was scanning my $HOME without me asking it do to that, BTW. Quickly, Pierre -- nowhere.man@levallois.eu.org OpenPGP 0xD9D50D8A