-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Andreas,
Andreas Krüger wrote: > I cannot run clisp without getting this error, see below. > (I'm a Lisp beginner.) 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. For example: [EMAIL PROTECTED]:~ :( $ ls | grep -v '^[-a-zA-Z0-9.]' [EMAIL PROTECTED]:~ :( $ LANG=C clisp ... [1]> (quit) Bye. [EMAIL PROTECTED]:~ :) $ touch 'élève' [EMAIL PROTECTED]:~ :) $ LANG=C clisp ... *** - invalid byte #xC3 in CHARSET:ASCII conversion The following restarts are available: ABORT :R1 ABORT ABORT :R2 ABORT ABORT :R3 ABORT ABORT :R4 ABORT ABORT :R5 ABORT Break 1 [6]> #xC3 is strange because the characters we used are é and è or E9 and E8, but in UTF8 it is encoded as #C3 #xA9 (see http://www.fileformat.info/info/unicode/char/00e9/index.htm). clisp stumbles across this file while searching for its .clisprc.lisp file in the home directory, and the error is normal as the filename it sees it not valid in the locale you've chosen. 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: LANG=en_GB.utf8 clisp or prevent clisp from searching for he rc file: LANG=C clisp -norc Groetjes, Peter - -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson| -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG9sRj11ldN0tyliURAkjbAKCvYzLEfqYaBrh7lMm31fZEEO3eTwCfT/qC AYXQ0Gaz1WsvGB5LTOUiaSA= =ETVj -----END PGP SIGNATURE-----
