-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Peter,
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! I had an ancient file with an ISO-8859-1 name in my $HOME. That name contained characters illegal in ASCII and also was not legal in UTF-8. Renaming that file solved the problem. For the record, that file name had nothing to do whatsoever with LISP / clisp.
It is unclear how to fix this, as it is normal that an error should be displayed an easy fix it to use a locale that uses UTF8
More precisely, "to use a locale that can display all file names in the $HOME directory". Which, in my case, was "ISO-8859-1".
clisp stumbles across this file while searching for its .clisprc.lisp file in the home directory,
Weird. Why does clisp think it needs to read my entire $HOME? As far as LISP is concerned, I'm a beginner. In other programming languages, I would have coded a "stat" to see whether ".clisprc.lisp" is there, and then an "open" if it is. Or else, I might have tried to open, and handle whatever "file not there" error I might get. Is it not straightforward to do this in LISP? Anyway. Thank you, Peter! Cheers, regards, warm greetings (on this sunny morning here in Germany) Andreas - -- andreas.krueger@famsik.de PGP-Schlüssel 0xA207E340 (http://www.pca.dfn.de/dfnpca/pgpkserv/) Fingerprint B46B C7BA FFEE AD41 35DD 49C3 9D6A E529 A207 E340 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.0 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG92fJnWrlKaIH40ARAqm6AKCLDhWXZEqYR1n6jslIFDGyg7BX7ACfRQkP IMV1fLQVhdMtp2zJ9IMdmy0= =cjRI -----END PGP SIGNATURE-----