Re: [clisp-list] open .mem file in emacs (windows)

Joerg,
Thanks for your reply. I think I didn't make myself completely clear (or I
am misunderstanding you), but the problem is not that CLISP won't open the
file. Image files are associated with CLISP. When I doubleclick an image,
CLISP loads it without any problem (no switches necessary). However, when I
try to load the file in EMACS, with CLISP as an inferior LISP, I get this
error message. And I don't think there are any switches associated with LOAD
in EMACS (but I may be wrong). So, the strange thing from my viewpoint is
that CLISP itself can open the image, unless you open it in EMACS running
CLISP as an inferior LISP. And since I want to be able to change the code
in the image, it would be nice to load it from EMACS since that has the
development utilities.
Dan.
----- Original Message -----
From: "Hoehle, Joerg-Cyril" <Joerg-Cyril.Hoehle@...>
To: <clisp-list@...>
Cc: <Daniel.Freudenthal@...>
Sent: Thursday, November 28, 2002 8:26 AM
Subject: [clisp-list] open .mem file in emacs (windows)
Dan wrote:
>but I'm encountering the following problem: If I dump an image using
saveinitmem
>and try to load it into clisp under EMACS, I get the following error
message:
>READ from #<INPUT BUFFERED FILE-STREAM CHARACTER #P"C:\\home\\filename.mem"
@1>: >illegal character #\Null
The error message shows that CLISP is not loading an image file, but
attempts to READ a Lisp (or .fas) file.
You probably got your -M option wrong.
When loading images, CLISP uses the OS' read() etc., so no message about
(Lisp)READ from the file #P"foo.mem" can appear.
Did you try and execute ...\lisp.exe -M C:\home\filename.mem -B xxx/ -E... ?
Regards,
Jörg Höhle.

Thread view

I've just installed CLISP 2.30 with EMACS following the Common LISP =
Cookbook guidelines. I've ported some code from MCL, and it appears to =
be working allright, but I'm encountering the following problem: If I =
dump an image using saveinitmem and try to load it into clisp under =
EMACS, I get the following error message:
READ from #<INPUT BUFFERED FILE-STREAM CHARACTER =
#P"C:\\home\\filename.mem" @1>: illegal character #\Null
Backtrace tells me: Character #\u2039 cannot be represented in the =
character set CHARSET:CP850.
All my functions and variables are now undefined, i.e the file failed to =
load.
When I load the image in CLISP proper (i.e. not using EMACS), everything =
works fine. I like to be able to load this file in EMACS, as I may want =
to add/change code to the image later (and this happens regularly, with =
the work I'm doing). I realise that this can be done in CLISP by loading =
the file with the new code, but it just seems rather inconvenient as =
CLISP itself doesn't quite give you the development environment that =
EMACS does, and it seems a bit silly to develop the code in an =
environment different from than the one you'll be using it in.
So, my question is:
Is this
A. Standard behaviour
B. Possible related to my setup
C. A bug
but, most importantly: how do I get around it?
I'm running CLISP 2.30 under winxp, as far as I know, all is set up =
according to the cookbook guidelines (no changes to EMACS either), and =
(so far) I'm not encountering any other problems. Any input is =
appreciated.
Cheers,
Dan.

Dan wrote:
>but I'm encountering the following problem: If I dump an image using =
saveinitmem
>and try to load it into clisp under EMACS, I get the following error =
message:
=20
>READ from #<INPUT BUFFERED FILE-STREAM CHARACTER =
#P"C:\\home\\filename.mem" @1>: >illegal character #\Null
The error message shows that CLISP is not loading an image file, but =
attempts to READ a Lisp (or .fas) file.
You probably got your -M option wrong.
When loading images, CLISP uses the OS' read() etc., so no message =
about (Lisp)READ from the file #P"foo.mem" can appear.
Did you try and execute ...\lisp.exe -M C:\home\filename.mem -B xxx/ =
-E... ?
Regards,
J=F6rg H=F6hle.

Joerg,
Thanks for your reply. I think I didn't make myself completely clear (or I
am misunderstanding you), but the problem is not that CLISP won't open the
file. Image files are associated with CLISP. When I doubleclick an image,
CLISP loads it without any problem (no switches necessary). However, when I
try to load the file in EMACS, with CLISP as an inferior LISP, I get this
error message. And I don't think there are any switches associated with LOAD
in EMACS (but I may be wrong). So, the strange thing from my viewpoint is
that CLISP itself can open the image, unless you open it in EMACS running
CLISP as an inferior LISP. And since I want to be able to change the code
in the image, it would be nice to load it from EMACS since that has the
development utilities.
Dan.
----- Original Message -----
From: "Hoehle, Joerg-Cyril" <Joerg-Cyril.Hoehle@...>
To: <clisp-list@...>
Cc: <Daniel.Freudenthal@...>
Sent: Thursday, November 28, 2002 8:26 AM
Subject: [clisp-list] open .mem file in emacs (windows)
Dan wrote:
>but I'm encountering the following problem: If I dump an image using
saveinitmem
>and try to load it into clisp under EMACS, I get the following error
message:
>READ from #<INPUT BUFFERED FILE-STREAM CHARACTER #P"C:\\home\\filename.mem"
@1>: >illegal character #\Null
The error message shows that CLISP is not loading an image file, but
attempts to READ a Lisp (or .fas) file.
You probably got your -M option wrong.
When loading images, CLISP uses the OS' read() etc., so no message about
(Lisp)READ from the file #P"foo.mem" can appear.
Did you try and execute ...\lisp.exe -M C:\home\filename.mem -B xxx/ -E... ?
Regards,
Jörg Höhle.