Yaroslav Kavenchuk wrote:

Surendra Singhi wrote:

...

Hello,

I recently upgraded to clisp 2.35 and now when I try to start slime on a lisp file, slime gets stuck.

The *inferior-lisp* buffer shows me the following restart.

** - Continuable Error INTERN("*DOCUMENTATION*"): #<PACKAGE SYSTEM> is locked If you continue (by typing 'continue'): Ignore the lock and proceed The following restarts are also available: SKIP :R1 skip (COMPILE-FILES-IF-NEEDED-SERIALLY #) STOP :R2 stop loading file C:\Program Files\XEmacs\xemacs-packages\lisp\slime-1.2.1\swank-loader.lisp ABORT :R3 ABORT

slime from xemacs? may be get slime from CVS head?

Same issue for me. Using xemacs and CVS head I think something in swank-clisp.lisp Have'nt time to track it down right now Cheers

Very odd. I think probably a stale fasl I recompiled swak outside of xemacs from the command line and it now works fine Surendra, you might try the same? Yaroslav Kavenchuk wrote:

David Hodge wrote:

...

...

...

Hello,

I recently upgraded to clisp 2.35 and now when I try to start slime on

a

...

...

lisp file, slime gets stuck.

The *inferior-lisp* buffer shows me the following restart.

** - Continuable Error INTERN("*DOCUMENTATION*"): #<PACKAGE SYSTEM> is locked If you continue (by typing 'continue'): Ignore the lock and proceed The following restarts are also available: SKIP :R1 skip (COMPILE-FILES-IF-NEEDED-SERIALLY #) STOP :R2 stop loading file C:\Program Files\XEmacs\xemacs-packages\lisp\slime-1.2.1\swank-loader.lisp ABORT :R3 ABORT

slime from xemacs? may be get slime from CVS head?

Same issue for me. Using xemacs and CVS head

I think something in swank-clisp.lisp Have'nt time to track it down right now

clisp 2.35, GNU emacs 22.0.51, slime from CVS head - no errors.

Surendra Singhi wrote:

David Hodge <david@hodge.id.au> writes:

...

Very odd.

I think probably a stale fasl

I recompiled swak outside of xemacs from the command line and it now works fine

Yes, using the cvs version of slime worked.

The slime release 1.2.1 uses the variable sys::*documentation*, which I think is no longer present in clisp 1.35 and this was causing the problem.

Thanks.

I'm not sure if my problem is related to the one above, but I'm not able to run xemacs, slime (version 1.2.1 or the cvs head (as of 10 jan 06)), with clisp 2.35. However, when I try to run slime, it fails more brutally. It gets to the [1]> prompt and then right after I get a "Process inferior-lisp segmentation fault". I'm running on OS X. But it all works fine in emacs. The slime "PROBLEMS" file mentions sometimes clisp needs to be invoked with "clisp -K full" but I can't find any elisp variable or customization setting that lets me set command line arguments to the lisp process. Anyone run into this problem? Is slime broken on xemacs/os x? alexis

David Hodge <david@hodge.id.au> writes:

Yaroslav Kavenchuk wrote:

...

Surendra Singhi wrote:

...

I recently upgraded to clisp 2.35 and now when I try to start slime on a lisp file, slime gets stuck.

The *inferior-lisp* buffer shows me the following restart.

** - Continuable Error INTERN("*DOCUMENTATION*"): #<PACKAGE SYSTEM> is locked If you continue (by typing 'continue'): Ignore the lock and proceed The following restarts are also available: SKIP :R1 skip (COMPILE-FILES-IF-NEEDED-SERIALLY #) STOP :R2 stop loading file C:\Program Files\XEmacs\xemacs-packages\lisp\slime-1.2.1\swank-loader.lisp ABORT :R3 ABORT

slime from xemacs? may be get slime from CVS head?

Same issue for me. Using xemacs and CVS head

I think something in swank-clisp.lisp Have'nt time to track it down right now

Thanks, I have reverted back to clisp-2.34 for time being. Maybe it is an XEmacs specific issue. -- Surendra Singhi http://www.public.asu.edu/~sksinghi/index.html "All animals are equal, but some animals are more equal than others." - Orwell, Animal Farm, 1945