Unfortunately there is no directory ~/.slime and there are no files *.fasl other than those accompanying the common lisp install. So I am unable to use this fix.
* Michael [2005-11-21 02:24+0100] writes:
Unfortunately there is no directory ~/.slime and there are no files *.fasl other than those accompanying the common lisp install. So I am unable to use this fix.
I have no idea how that can be. Creating the ~/.slime dir is about the first thing we do. Maybe it's a Gentoo issue?
+ Helmut Eller heller@common-lisp.net:
| * Michael [2005-11-21 02:24+0100] writes: | | > Unfortunately there is no directory ~/.slime and there are no files | > *.fasl other than those accompanying the common lisp install. So I | > am unable to use this fix. | | I have no idea how that can be. Creating the ~/.slime dir is about | the first thing we do. Maybe it's a Gentoo issue?
That is odd indeed. You seem to be using sbcl. What version?
You also seem to get a functioning *inferior-lisp* buffer. What do you get if you evaluate (swank-loader::binary-pathname #P"foo.lisp") in it? Or (user-homedir-pathname)?
As far as I can tell from the code, ~/.slime is not created as a separate step, but impicitly through a call to ensure-directories-exist when compiling source files.
Oh, and there should be a swank-loader.fasl in the slime directory. It should get recompiled automatically if swank-loader.lisp is changed, but you may wish to remove it just in case.
- Harald
Harald Hanche-Olsen <hanche <at> math.ntnu.no> writes:
You also seem to get a functioning *inferior-lisp* buffer. What do you get if you evaluate (swank-loader::binary-pathname #P"foo.lisp") in it? Or (user-homedir-pathname)?
Cannot do these evaluations because it is this buffer that is hung.
As far as I can tell from the code, ~/.slime is not created as a separate step, but impicitly through a call to ensure-directories-exist when compiling source files.
Oh, and there should be a swank-loader.fasl in the slime directory. It should get recompiled automatically if swank-loader.lisp is changed, but you may wish to remove it just in case.
No such file found. Found swank-loader.lisp though.
Thanks for the reply.
I'm running Gentoo and creating ~/.slime is definitely about the first thing it does. No problems there.
--Jeff
On Tue Nov 22, 2005 at 11:39:23AM +0100, Helmut Eller wrote:
- Michael [2005-11-21 02:24+0100] writes:
Unfortunately there is no directory ~/.slime and there are no files *.fasl other than those accompanying the common lisp install. So I am unable to use this fix.
I have no idea how that can be. Creating the ~/.slime dir is about the first thing we do. Maybe it's a Gentoo issue? _______________________________________________ slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel
On Wed Nov 23, 2005 at 02:45:25AM +0000, Michael wrote:
That seems odd since the Gentoo slime maintainer says that Gentoo does not create ~/.slime. See the post above for details.
I'm running Gentoo and creating ~/.slime is definitely about the first thing it does. No problems there.
We're either crossing posts or you missed my subsequent post: Gentoo's port of slime is usually too old. Grab the one off CVS which works the way it is supposed to - creates the ~/slime/fasl tree.
--Jeff
slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel
Helmut Eller <heller <at> common-lisp.net> writes:
- Michael [2005-11-21 02:24+0100] writes:
Unfortunately there is no directory ~/.slime and there are no files *.fasl other than those accompanying the common lisp install. So I am unable to use this fix.
I have no idea how that can be. Creating the ~/.slime dir is about the first thing we do. Maybe it's a Gentoo issue?
Yes, it is a Gentoo thing. I received this reply from the Gentoo maintainer:
"There is no ~/.slime FASL cache because the Gentoo ports are created to use the general cache in /var/cache/common-lisp-controller. If you are using SBCL, try removing old FASLs from there using this command:
"rm -rf /var/cache/common-lisp-controller/<your-username>/sbcl/*"
Unfortunately, after executing this command slime still hangs exactly as before.
Any ideas?
On Wed Nov 23, 2005 at 02:37:32AM +0000, Michael wrote:
Helmut Eller <heller <at> common-lisp.net> writes:
- Michael [2005-11-21 02:24+0100] writes:
Unfortunately there is no directory ~/.slime and there are no files *.fasl other than those accompanying the common lisp install. So I am unable to use this fix.
I have no idea how that can be. Creating the ~/.slime dir is about the first thing we do. Maybe it's a Gentoo issue?
Yes, it is a Gentoo thing. I received this reply from the Gentoo maintainer:
"There is no ~/.slime FASL cache because the Gentoo ports are created to use the general cache in /var/cache/common-lisp-controller. If you are using SBCL, try removing old FASLs from there using this command:
"rm -rf /var/cache/common-lisp-controller/<your-username>/sbcl/*"
Unfortunately, after executing this command slime still hangs exactly as before.
Any ideas?
I run slime on Gentoo, but I don't use the Gentoo port. Try installing slime out of CVS directly. Then it creates the ~/.slime directory like its supposed to and everything works.
--Jeff Cunningham
I run slime on Gentoo, but I don't use the Gentoo port. Try installing slime out of CVS directly. Then it creates the ~/.slime directory like its supposed to and everything works.
--Jeff Cunningham
Thanks for the reply, Jeff. Actually, I did try that. However, it also did not work for the same reason. That is, the CVS version of slime had exactly the same problem. It did not create the ~/.slime dir.
The problem has ceased since I unmerged slime, ran the "rm" command to empty the cache, and then re-emerged slime. Now the REPL comes up normally using the Gentoo port. For how long? Don't know.
Il 2005-11-23, Michael m.labhard@comcast.net ha scritto:
I have no idea how that can be. Creating the ~/.slime dir is about the first thing we do. Maybe it's a Gentoo issue?
Yes, it is a Gentoo thing. I received this reply from the Gentoo maintainer:
For future reference: this is also feature of the debian port. The cl-swank library will create
pve@sharrow:~ :) $ls -l /var/cache/common-lisp-controller/pve/sbcl/swank/fasl/sbcl-0.9.6-linux-x86/ total 3556 -rw-r--r-- 1 pve pve 52530 2005-11-16 10:56 nregex.fasl -rw-r--r-- 1 pve pve 433443 2005-11-16 10:56 swank-backend.fasl -rw-r--r-- 1 pve pve 1156862 2005-11-16 10:56 swank.fasl -rw-r--r-- 1 pve pve 81403 2005-11-16 10:56 swank-gray.fasl -rw-r--r-- 1 pve pve 1826522 2005-11-16 10:56 swank-sbcl.fasl -rw-r--r-- 1 pve pve 33069 2005-11-16 10:56 swank-source-file-cache.fasl -rw-r--r-- 1 pve pve 27646 2005-11-16 10:56 swank-source-path-parser.fasl
So far there have been no complaints about this yet.
Groetjes, Peter
-
Harald Hanche-Olsen -
Helmut Eller -
Jeff Cunningham -
Michael -
Peter Van Eynde