From: Marek S. <st...@fs...> - 2007-03-08 15:15:01
|
Hello experts! Has anybody encountered this behavior after launching the clisp? > stefan:~ $ clisp > i i i i i i i ooooo o ooooooo ooooo ooooo > I I I I I I I 8 8 8 8 8 o 8 8 > I \ `+' / I 8 8 8 8 8 8 > \ `-+-' / 8 8 8 ooooo 8oooo > `-__|__-' 8 8 8 8 8 > | 8 o 8 8 o 8 8 > ------+------ ooooo 8oooooo ooo8ooo ooooo 8 > Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 > Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 > Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 > Copyright (c) Bruno Haible, Sam Steingold 1999-2000 > Copyright (c) Sam Steingold, Bruno Haible 2001-2006 > *** - invalid byte sequence #xE1 #x6B #x20 in CHARSET:UTF-8 conversion > The following restarts are available: > ABORT :R1 ABORT > ABORT :R2 ABORT > Break 1 [3]> I'm using openSUSE 10.2, kernel-2.6.18, clisp version 2.39. Thank you for any hints or explanations. Regards Stefan |
From: Sam S. <sd...@gn...> - 2007-03-08 15:57:00
|
Marek Stefan wrote: > Has anybody encountered this behavior after launching the clisp? > >> stefan:~ $ clisp > >> *** - invalid byte sequence #xE1 #x6B #x20 in CHARSET:UTF-8 conversion >> The following restarts are available: >> ABORT :R1 ABORT >> ABORT :R2 ABORT >> Break 1 [3]> > > I'm using openSUSE 10.2, kernel-2.6.18, clisp version 2.39. http://clisp.cons.org/impnotes/faq.html#faq-enc-err (look for non-UTF chars in pathnames) your question was answered with an FAQ link. the fine for asking questions before consulting the FAQ list is $10. |
From: Pascal B. <pj...@in...> - 2007-03-08 16:19:27
|
Sam Steingold writes: > Marek Stefan wrote: > > Has anybody encountered this behavior after launching the clisp? > > > >> stefan:~ $ clisp > > > >> *** - invalid byte sequence #xE1 #x6B #x20 in CHARSET:UTF-8 conversion > >> The following restarts are available: > >> ABORT :R1 ABORT > >> ABORT :R2 ABORT > >> Break 1 [3]> > > > > I'm using openSUSE 10.2, kernel-2.6.18, clisp version 2.39. > > http://clisp.cons.org/impnotes/faq.html#faq-enc-err > (look for non-UTF chars in pathnames) > > your question was answered with an FAQ link. > the fine for asking questions before consulting the FAQ list is $10. Perhaps it would be a good idea to add this link to this very error message, at least when it appears before the first prompt... -- __Pascal Bourguignon__ http://www.informatimago.com/ Un chat errant se soulage dans le jardin d'hiver Shiki |
From: Marek S. <st...@fs...> - 2007-03-08 16:20:20
|
>> Has anybody encountered this behavior after launching the clisp? >> >>> stefan:~ $ clisp >> >>> *** - invalid byte sequence #xE1 #x6B #x20 in CHARSET:UTF-8 > conversion >>> The following restarts are available: >>> ABORT :R1 ABORT >>> ABORT :R2 ABORT >>> Break 1 [3]> >> I'm using openSUSE 10.2, kernel-2.6.18, clisp version 2.39. > > http://clisp.cons.org/impnotes/faq.html#faq-enc-err(look for non-UTF chars in pathnames) > > your question was answered with an FAQ link. > the fine for asking questions before consulting the FAQ list is $10. Oh, sorry. Thank you! Stefan |
From: Sam S. <sd...@gn...> - 2007-03-09 14:04:04
|
Marek Stefan wrote: >>> Has anybody encountered this behavior after launching the clisp? >>> >>>> stefan:~ $ clisp >>>> *** - invalid byte sequence #xE1 #x6B #x20 in CHARSET:UTF-8 >> conversion >>>> The following restarts are available: >>>> ABORT :R1 ABORT >>>> ABORT :R2 ABORT >>>> Break 1 [3]> >>> I'm using openSUSE 10.2, kernel-2.6.18, clisp version 2.39. >> http://clisp.cons.org/impnotes/faq.html#faq-enc-err(look for non-UTF chars in pathnames) >> >> your question was answered with an FAQ link. >> the fine for asking questions before consulting the FAQ list is $10. > > Oh, sorry. Thank you! http://clisp.podval.org/impnotes/faq.html#faq-fine |