Re: Clisp+Emacs

[Sam Steingold]

> * In message <Pine.SUN.3.91.1010613113834.16126G-100000@is>
> * On the subject of "Re: Clisp+Emacs"
> * Sent on Wed, 13 Jun 2001 11:38:54 +0300
> * Honorable eliz@is.elta.co.il (Eli Zaretskii) writes:
>
> (Btw, if clisp indeed chokes when it gets CR-LF instead of just LF,
> IMHO that's a bug in the Windows port of clisp: it should support the
> format of text native to the OS it runs on.)

Actually, CLISP has excellent I18N facilities.
It handles UNICODE as well as every other extant encoding.

It works just fine in windows console and it can read files with any EOF
conventions (UNIX, DOS or MAC) on any platform (e.g., DOS files on a
MAC).

The problem does exist (and is generic on all platforms), and I hope to
address it, but it manifests itself only with "commands" (like "help" or
"step", which must not have any whitespace around them), not with CL
forms.

-- 
Sam Steingold (http://www.podval.org/~sds)
Who is General Failure and why is he reading my hard disk?