From: Yves C. <yc...@cl...> - 2006-09-27 07:02:12
|
Hello. I could compile clisp-2.39 on an Intel Mac running Mac OS X 10.4.7. It passed all tests and seems to work normally but if I try and exit I get this: [1]> (quit) *** - Le *** - Le *** - Le *** - Message inimprimable (non printable message) Break 1 [2]> (quit) *** - Message inimprimable Break 1 [3]> (quit) *** - Le *** - Message inimprimable Break 1 [4]> The same thing happens with (bye), (exit) and Ctrl D. With Ctrl C it enters an infinite loop. Am I doing something wrong? Regards, YC |
From: Pascal B. <pj...@in...> - 2006-09-27 19:27:31
|
Yves Codet writes: > Hello. >=20 > I could compile clisp-2.39 on an Intel Mac running Mac OS X 10.4.7. =20 > It passed all tests and seems to work normally but if I try and exit =20 > I get this: >=20 > [1]> (quit) >=20 > *** - Le > *** - Le > *** - Le > *** - Message inimprimable (non printable message) > Break 1 [2]> (quit) >=20 > *** - Message inimprimable > Break 1 [3]> (quit) >=20 > *** - Le > *** - Message inimprimable > Break 1 [4]> >=20 > The same thing happens with (bye), (exit) and Ctrl D. With Ctrl C it =20 > enters an infinite loop. Am I doing something wrong? The unprintable message may contain characters that cannot be encoded in the coding system you've selected for terminal output. Try another coding system, like iso-8859-1 (should be enough for French) or utf-8. On MacOSX, since the file names are stored in utf-8 too, you could configure your editor to save all the files in utf-8 and just use: clisp -ansi -E utf-8 to set all the coding systems to utf-8. The function QUIT is in the package EXT. (EXT:QUIT) should always work... --=20 __Pascal Bourguignon__ http://www.informatimago.com/ This is a signature virus. Add me to your signature and help me to live. |
From: Yves C. <yc...@cl...> - 2006-09-28 06:55:17
|
Le 27 sept. 06 =E0 14:59, Sam Steingold a =E9crit : > apparently, your language settings (French) are inconsistent with your > encoding settings (ASCII). > what is your $LANG? Clisp says that $LANG has no value: [1]> (system::getenv $LANG) *** - EVAL: La variable $LANG n'a pas de valeur. Rentr=E9es possibles: USE-VALUE :R1 You may input a value to be used instead of =20 $LANG. STORE-VALUE :R2 You may input a new value for $LANG. ABORT :R3 ABORT It's writing in French though (sorry about my ignorant remarks, I'm =20 quite new to Clisp and Lisp). Yves Codet |
From: Pascal B. <pj...@in...> - 2006-09-28 08:34:45
|
Yves Codet writes: >=20 > Le 27 sept. 06 =C3=A0 14:59, Sam Steingold a =C3=A9crit : >=20 > > apparently, your language settings (French) are inconsistent with you= r > > encoding settings (ASCII). > > what is your $LANG? >=20 > Clisp says that $LANG has no value: >=20 > [1]> (system::getenv $LANG) > *** - EVAL: La variable $LANG n'a pas de valeur. ELANG :-) $LANG is expressed in shell language. To get the value of an environment variable from Lisp (or from C), we must give the _name_ of the shell environment variable to the getenv func= tion. (ext:getenv "LANG") > It's writing in French though (sorry about my ignorant remarks, I'm =20 > quite new to Clisp and Lisp). No problem. Most native English speakers haven't learned English as foreign language. --=20 __Pascal Bourguignon__ http://www.informatimago.com/ Grace personified, I leap into the window. I meant to do that. |
From: Yves C. <yc...@cl...> - 2006-09-28 08:50:37
|
Le 28 sept. 06 =E0 10:34, Pascal Bourguignon a =E9crit : > To get the value of an environment variable from Lisp (or from C), we > must give the _name_ of the shell environment variable to the =20 > getenv function. > > (ext:getenv "LANG") I get this: [1]> (ext:getenv "LANG") NIL Yves Codet |
From: Yves C. <yc...@cl...> - 2006-09-28 09:43:10
|
Hello. Apparently the problem was that my $LANG variable had no value. If I set it to fr_FR.UTF-8, I can invoke Clisp simply as clisp (without - ansi -E utf-8); it can print its message and exit normally. Best wishes, Yves Codet |