Latest version of SBCL on Debian, latest SLIME on CVS: I have the image running, try slime-connect, and nothing happens. It doesn't matter if SBCL is running under attachtty or not.
When I start SBCL with SLIME (with the "slime" Emacs function), then it starts, but the start-up process stops several times and continues only after I press some key - any key.
Any clue?
vedm mlist@rogers.com writes:
Latest version of SBCL on Debian, latest SLIME on CVS: I have the image running, try slime-connect, and nothing happens. It doesn't matter if SBCL is running under attachtty or not.
When I start SBCL with SLIME (with the "slime" Emacs function), then it starts, but the start-up process stops several times and continues only after I press some key - any key.
Any clue?
More details, please.
Which SBCL version? Does it matter what you have in the image. Do you start swank server in the image before connecting? Which Emacs version? At what point does the start-up process stop? Etc.
Cheers,
-- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs."
Nikodemus Siivola nikodemus@random-state.net writes:
vedm mlist@rogers.com writes:
Latest version of SBCL on Debian, latest SLIME on CVS: I have the image running, try slime-connect, and nothing happens. It doesn't matter if SBCL is running under attachtty or not.
When I start SBCL with SLIME (with the "slime" Emacs function), then it starts, but the start-up process stops several times and continues only after I press some key - any key.
Any clue?
More details, please.
Which SBCL version? Does it matter what you have in the image. Do you start swank server in the image before connecting? Which Emacs version? At what point does the start-up process stop? Etc.
Emacs version: GNU Emacs 21.4.1 (i486-pc-linux-gnu, X toolkit, Xaw3d scroll bars).
SBCL is the latest Debian package, version 1.0, it starts like this: ==== This is SBCL 1.0, an implementation of ANSI Common Lisp. More information about SBCL is available at http://www.sbcl.org/.
SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. ;; loading #P"/home/myhome/.slime/fasl/2006-11-26/sbcl-1.0-linux-x86/swank-backend.fasl" ;; loading #P"/home/myhome/.slime/fasl/2006-11-26/sbcl-1.0-linux-x86/nregex.fasl" ;; loading #P"/home/myhome/.slime/fasl/2006-11-26/sbcl-1.0-linux-x86/swank-sbcl.fasl" ;; loading #P"/home/myhome/.slime/fasl/2006-11-26/sbcl-1.0-linux-x86/swank-source-path-parser.fasl" ;; loading #P"/home/myhome/.slime/fasl/2006-11-26/sbcl-1.0-linux-x86/swank-source-file-cache.fasl" ;; loading #P"/home/myhome/.slime/fasl/2006-11-26/sbcl-1.0-linux-x86/swank-gray.fasl" ;; loading #P"/home/myhome/.slime/fasl/2006-11-26/sbcl-1.0-linux-x86/swank.fasl" WARNING: These Swank interfaces are unimplemented: [CALLS-WHO DISASSEMBLE-FRAME SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN WHO-BINDS WHO-CALLS WHO-MACROEXPANDS WHO-REFERENCES WHO-SETS WHO-SPECIALIZES] ;; Swank started at port: 4005. ===
Then I do slime-connect - in the echo area I see "Connecting to Swank on port 4005", and then nothing happens, neither on Emacs or on the SBCL side.
I start SBCL like this:
detachtty --dribble-file $HOME/tmp/lisp-server/lisp-dribble \ --log-file $HOME/tmp/lisp-server/detachtty.log \ --pid-file $HOME/tmp/lisp-server/lisp.pid \ $HOME/tmp/lisp-server/lisp-socket \ /usr/bin/sbcl \ --no-userinit \ --eval "(require 'swank)" \ --eval "(setq *debug-io* *standard-output*)" \ --eval "(swank:create-swank-server 4005)" \
* vedm [2006-12-05 05:53+0100] writes:
I start SBCL like this:
detachtty --dribble-file $HOME/tmp/lisp-server/lisp-dribble \ --log-file $HOME/tmp/lisp-server/detachtty.log \ --pid-file $HOME/tmp/lisp-server/lisp.pid \ $HOME/tmp/lisp-server/lisp-socket \ /usr/bin/sbcl \ --no-userinit \ --eval "(require 'swank)" \ --eval "(setq *debug-io* *standard-output*)" \ --eval "(swank:create-swank-server 4005)" \
Does it work if you use swank:create-server instead of create-swank-server?
Helmut Eller heller@common-lisp.net writes:
- vedm [2006-12-05 05:53+0100] writes:
I start SBCL like this:
detachtty --dribble-file $HOME/tmp/lisp-server/lisp-dribble \ --log-file $HOME/tmp/lisp-server/detachtty.log \ --pid-file $HOME/tmp/lisp-server/lisp.pid \ $HOME/tmp/lisp-server/lisp-socket \ /usr/bin/sbcl \ --no-userinit \ --eval "(require 'swank)" \ --eval "(setq *debug-io* *standard-output*)" \ --eval "(swank:create-swank-server 4005)" \
Does it work if you use swank:create-server instead of create-swank-server?
Yes it does, thanks for the hint. What's the difference between these two then?
* vedm [2006-12-05 18:15+0100] writes:
Helmut Eller heller@common-lisp.net writes:
Does it work if you use swank:create-server instead of create-swank-server?
Yes it does, thanks for the hint. What's the difference between these two then?
create-swank-server was the old version with only optional parameters. create-server takes only keyword arguments and was intended to replace create-swank-server, but for some reason we forgot to delete the old version.
Helmut.
-
Helmut Eller -
Nikodemus Siivola -
vedm