Am Thu, 23 Dec 2004 04:12:13 -0700 schrieb Surendra Singhi <efuzzyone@netscape.net>:
Any suggestions on what should I do to ensure that slime and inferior lisp connects to the right clisp and starts up properly.
FWIW here's my working configuration: --- init.el -------------------------------------------------- (add-to-list 'load-path "~/Eigene Dateien/devel/lisp/slime") (require 'slime) (add-hook 'lisp-mode-hook (lambda () (slime-mode t))) (add-hook 'inferior-lisp-mode-hook (lambda () (inferior-slime-mode t))) [...] (defun clisp-start () (interactive) (shell-command (concat "C:\\Programme\\clisp\\clisp-2.33.1\\base\\lisp.exe " "-B \"C:/Programme/clisp/clisp-2.33.1/\" " "-M \"C:/Programme/clisp/clisp-2.33.1/base/lispinit.mem\" " "-i \"C:/Dokumente und Einstellungen/Tommy/slime.lisp\" " "-ansi -q&")) (sleep-for 1) (slime-connect "localhost" 4005) (cd "~/Eigene Dateien/")) --- slime.lisp ----------------------------------------------- (load "C:/Dokumente und Einstellungen/Tommy/Eigene Dateien/devel/lisp/slime/swank-loader.lisp") (swank:create-server) That is I start up the swank-server independently and later connect to it. The (sleep-for 1) construct is a bit ugly since it may take longer than 1 second to start up swank in which case you have to manually call M-x slime-connect some seconds later. HTH -ts -- ,, \../ / <<< The LISP Effect |_\\ _==__ __ | |bb| | _________________________________________________