[slime-devel] Windows + CLisp: wrong path separator?
Hello, I'm trying to run SLIME (snapshot of 2010 July 06) with native (that is, not Cygwinized) CLisp 2.49. When I started SLIME, CLisp complained it couldn't find "swank-loader.lisp" with provided full path, which had backslashes. Therefore, I setted `slime-backend' to full path of `swank-loader.lisp', but using slashes, and that worked. Now, CLisp complains that it can't find the directory: - OPEN: Directory #P"C:\\DOCUME~1\\USERR~2\\IMPOST~1\\Temp\\" does not exist Such directory does exist. Should I replace backslashes with slashes here too, maybe? But I don't know what variable to set. My setup is like this: (setq inferior-lisp-program "C:/Programmi/clisp-2.49/clisp.exe -K full") (setq slime-net-coding-system 'iso-latin-1-unix) (require 'slime) (slime-setup '(slime-fancy)) Any hints? Thanks. Elena
* egarrulo [2010-07-30 15:13] writes:
Hello,
I'm trying to run SLIME (snapshot of 2010 July 06) with native (that is, not Cygwinized) CLisp 2.49.
When I started SLIME, CLisp complained it couldn't find "swank-loader.lisp" with provided full path, which had backslashes. Therefore, I setted `slime-backend' to full path of `swank-loader.lisp', but using slashes, and that worked.
Now, CLisp complains that it can't find the directory:
- OPEN: Directory #P"C:\\DOCUME~1\\USERR~2\\IMPOST~1\\Temp\\" does not exist
Such directory does exist. Should I replace backslashes with slashes here too, maybe? But I don't know what variable to set.
The value comes from temporary-file-directory inside Emacs. Maybe it works if you set that to the full directory name (with /-es but without ~1 thingies). If CLISP can't do (open "C:\\DOCUME~1\\USERR~2\\IMPOST~1\\Temp\\x.x" :if-does-not-exist :create) it's arguably a CLISP bug. Helmut
Using a long file name for the `temporary-file-directory' worked. Thank you. It seems CLisp can't handle short paths. I'll let the maintainer know. Cheers. 2010/7/30 Helmut Eller <heller@common-lisp.net>:
* egarrulo [2010-07-30 15:13] writes:
Now, CLisp complains that it can't find the directory:
- OPEN: Directory #P"C:\\DOCUME~1\\USERR~2\\IMPOST~1\\Temp\\" does not exist
Such directory does exist. Should I replace backslashes with slashes here too, maybe? But I don't know what variable to set.
The value comes from temporary-file-directory inside Emacs. Maybe it works if you set that to the full directory name (with /-es but without ~1 thingies).
If CLISP can't do (open "C:\\DOCUME~1\\USERR~2\\IMPOST~1\\Temp\\x.x" :if-does-not-exist :create) it's arguably a CLISP bug.
Helmut
_______________________________________________ slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel
I'm trying to run SLIME (snapshot of 2010 July 06) with native (that is, not Cygwinized) CLisp 2.49.
When I started SLIME, CLisp complained it couldn't find "swank-loader.lisp" with provided full path, which had backslashes. Therefore, I setted `slime-backend' to full path of `swank-loader.lisp', but using slashes, and that worked.
Now, CLisp complains that it can't find the directory:
- OPEN: Directory #P"C:\\DOCUME~1\\USERR~2\\IMPOST~1\\Temp\\" does not exist
Such directory does exist. Should I replace backslashes with slashes here too, maybe? But I don't know what variable to set.
My setup is like this:
(setq inferior-lisp-program "C:/Programmi/clisp-2.49/clisp.exe -K full") (setq slime-net-coding-system 'iso-latin-1-unix) (require 'slime) (slime-setup '(slime-fancy))
Not sure if that's really the problem but I had similar quirks with CLISP 2.49 under Debian Lenny and the solution was: CLISP 2.49 has no more "-K full", so just try: (setq inferior-lisp-program "C:/Programmi/clisp-2.49/clisp.exe") without the "-K full" it works with me, but haven't tested this on Windows yet... - edgar -- The author of this email does not necessarily endorse the following advertisements, which are the sole responsibility of the advertiser:
2010/7/30 edgar <edgar-rft@web.de>:
CLISP 2.49 has no more "-K full", so just try:
(setq inferior-lisp-program "C:/Programmi/clisp-2.49/clisp.exe")
without the "-K full" it works with me, but haven't tested this on Windows yet...
Thank you for your advice. Indeed, "clisp.exe" does work without any arguments. According to "clisp --help", "-K" is still supported on CLISP 2.49 on Windows: -K linkingset - use this executable and memory image Have a nice day.
participants (3)
-
edgar -
egarrulo -
Helmut Eller