slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] Current way to use multiple lisp implementations?
by Cody Koeninger 01 Nov '05

01 Nov '05

I'd like to be able to easily choose between several lisp implementations when starting slime (sbcl, cmucl, clisp). The most recent message I was able to find, on http://article.gmane.org/gmane.lisp.slime.devel/3932 suggested using slime-register-lisp-implementation, but I see that this function has been deleted. What's the current 'right' way to do this?

5 8

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 31 Oct '05

31 Oct '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.803 slime/ChangeLog:1.804 --- slime/ChangeLog:1.803 Sun Oct 30 18:07:14 2005 +++ slime/ChangeLog Mon Oct 31 09:26:54 2005 @@ -1,6 +1,17 @@ +2005-10-31 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-start, slime-lookup-lisp-implementation) + (slime-set-connection-info): Add a :name property for the + implementation and use it to derive the connection-name. + (slime-lisp-implementation-name): Renamed from + slime-lisp-implementation-type-name. + + * swank.lisp (simple-serve-requests): Add an extra abort restart. + (connection-info): Rename :type-name to :name. + 2005-10-30 Andras Simon <andras(a)renyi.hu> - * swank-abcl.lisp (inspect-for-emacs): Track mop changes in ABCL. + * swank-abcl.lisp (inspect-for-emacs): Track mop changes in ABCL. 2005-10-30 Helmut Eller <heller(a)common-lisp.net>

1 0

[slime-devel] Slime lockup after returning from SLDB
by Jonathan Lee 31 Oct '05

31 Oct '05

I am running the CVS of SLIME as of 27-Oct-2005 in GNU Emacs 21.3.1 on Windows XP using CLISP 2.35 as the backend. After aborting an error that throws me into the SLDB I get no prompt in the SLIME REPL. If I try to evaluate a form or variable (or even a blank line), I get the following in the mini-buffer: ;pipelined request... (swank:listener-eval "form I evaluated") If I try to evaluate a form in another buffer I get a similar response: ;pipelined request... (swank:interactive-eval "form I evaluated") The inferior-lisp buffer seems to still be working perfectly when I evaluate a test form in it. I've discovered that if I use "M-x slime" I can get SLIME to break out of this lockup, but this is definitely non-optimal. Any help with this would be appreciated. Jonathan Lee (format t "~A(a)~A.~A" '2jlee 'earthlink 'net)

6 10

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 30 Oct '05

30 Oct '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.801 slime/ChangeLog:1.803 --- slime/ChangeLog:1.801 Sun Oct 23 10:53:00 2005 +++ slime/ChangeLog Sun Oct 30 18:07:14 2005 @@ -1,3 +1,21 @@ +2005-10-30 Andras Simon <andras(a)renyi.hu> + + * swank-abcl.lisp (inspect-for-emacs): Track mop changes in ABCL. + +2005-10-30 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-eval): Ensure that the connection is open before + waiting for input. + + * swank.lisp (simple-serve-requests): Close the connection at the + end. + +2005-10-23 Harald Hanche-Olsen <hanche(a)math.ntnu.no> + + * slime.el (slime-init-keymaps): Use vectors when defining keys, + because e.g. (define-key (string ?\C-c) ...) doesn't work in the + emacs-unicode-2 branch. + 2005-10-23 Stefan Kamphausen <skampi(a)gmx.net> * slime.el (slime-repl-history-size, slime-repl-history-file): Use

1 0

Re: [slime-devel] Re: Slime lockup after returning from SLDB
by Jonathan Lee 29 Oct '05

29 Oct '05

While reading through the manual I ran across the the SWANK:*LOG-EVENTS* variable and turned it on. The log values were written to the SLIME REPL once it was created. Here are the statements logged in the REPL after I evaluated the '(error "foo") form: CL-USER> (error "foo") READ: (:emacs-rex (swank:listener-eval "(error \"foo\") ") "COMMON-LISP-USER" :repl-thread 3) DISPATCHING: (:EMACS-REX (SWANK:LISTENER-EVAL "(error \"foo\") ") "COMMON-LISP-USER" :REPL-THREAD 3) DISPATCHING: (:DEBUG 0 1 ("foo" " [Condition of type SIMPLE-ERROR]" NIL NIL) (("ABORT-REQUEST" "Abort handling SLIME request.") ("ABORT" "ABORT")) ((0 "#<SYSTEM-FUNCTION ERROR> 1") (1 "#<SYSTEM-FUNCTION EVAL>") (2 "#<COMPILED-FUNCTION SWANK::EVAL-REGION>") (3 "#<COMPILED-FUNCTION SWANK::LISTENER-EVAL-1>") (4 "#<COMPILED-FUNCTION #:|272 274 (DEFINTERFACE CALL-WITH-SYNTAX-HOOKS (FN) ...)-31-3-1-1|>") (5 "#<COMPILED-FUNCTION SWANK::CALL-WITH-BUFFER-SYNTAX>") (6 "#<COMPILED-FUNCTION SWANK:LISTENER-EVAL>") (7 "#<SYSTEM-FUNCTION EVAL>") (8 "#<COMPILED-FUNCTION SWANK::EVAL-FOR-EMACS-1>") (9 "#<COMPILED-FUNCTION #:|449 454 (DEFINTERFACE CALL-WITH-DEBUGGER-HOOK (HOOK FUN) ...)-50-3-1-1|>") ...) (3)) WRITE: (:debug 0 1 ("foo" " [Condition of type SIMPLE-ERROR]" nil nil) (("ABORT-REQUEST" "Abort handling SLIME request.") ("ABORT" "ABORT")) ((0 "#<SYSTEM-FUNCTION ERROR> 1") (1 "#<SYSTEM-FUNCTION EVAL>") (2 "#<COMPILED-FUNCTION SWANK::EVAL-REGION>") (3 "#<COMPILED-FUNCTION SWANK::LISTENER-EVAL-1>") (4 "#<COMPILED-FUNCTION #:|272 274 (DEFINTERFACE CALL-WITH-SYNTAX-HOOKS (FN) ...)-31-3-1-1|>") (5 "#<COMPILED-FUNCTION SWANK::CALL-WITH-BUFFER-SYNTAX>") (6 "#<COMPILED-FUNCTION SWANK:LISTENER-EVAL>") (7 "#<SYSTEM-FUNCTION EVAL>") (8 "#<COMPILED-FUNCTION SWANK::EVAL-FOR-EMACS-1>") (9 "#<COMPILED-FUNCTION #:|449 454 (DEFINTERFACE CALL-WITH-DEBUGGER-HOOK (HOOK FUN) ...)-50-3-1-1|>") (10 "#<COMPILED-FUNCTION SWANK::EVAL-FOR-EMACS>") (11 "#<COMPILED-FUNCTION SWANK::READ-FROM-EMACS>") (12 "#<COMPILED-FUNCTION SWANK::HANDLE-REQUEST-1>") (13 "#<COMPILED-FUNCTION SWANK::CALL-WITH-CONNECTION-1>") (14 "#<COMPILED-FUNCTION SWANK::CALL-WITH-REDIRECTED-IO>") (15 "#<COMPILED-FUNCTION SWANK::MAYBE-CALL-WITH-IO-REDIRECTION>") (16 "#<COMPILED-FUNCTION SWANK::CALL-WITH-CONNECTION>") (17 "#<COMPILED-FUNCTION SWANK::HANDLE-REQUEST>") (18 "#<COMPILED-FUNCTION SWANK::SIMPLE-SERVE-REQUESTS-2>") (19 "#<COMPILED-FUNCTION SWANK::SIMPLE-SERVE-REQUESTS>")) (3)) DISPATCHING: (:DEBUG-ACTIVATE 0 1) WRITE: (:debug-activate 0 1) READ: (:emacs-rex (swank:sldb-abort) nil 0 4) DISPATCHING: (:EMACS-REX (SWANK:SLDB-ABORT) NIL 0 4) DISPATCHING: (:RETURN 0 (:ABORT) 4) WRITE: (:return (:abort) 4) DISPATCHING: (:DEBUG-RETURN 0 1 NIL) WRITE: (:debug-return 0 1 nil) DISPATCHING: (:RETURN 0 (:ABORT) 3) WRITE: (:return (:abort) 3) ; Evaluation aborted

1 0

[slime-devel] Error on startup: Servname not supported
by Stuart Bain 26 Oct '05

26 Oct '05

Greetings all, I installed slime from CVS HEAD today (2005-10-26), and modified my init.el per the README; however, when I went to start slime, I ran into some problems. Specifically, the command buffer in emacs states: itimer "run-with-timer" signaled: (error "127.0.0.1/(^W1^H& Servname not supported for ai_socktype") I'm running XEmacs 21.4.17, and my clisp --version reports Software: GNU C 4.0.2. I'm running on the "breezy" version of Kubuntu Linux (Ubuntu). Has anyone run into this before? I'm new to Lisp and installing slime so I can go through some of the examples and exercises in the PCL book. Any and all assistance would be greatly appreciated. Best regards, -- Stuart

1 0

[slime-devel] Slime license annoyances
by Peter Van Eynde 25 Oct '05

25 Oct '05

Hello, I just got a reject from ftpmaster (the person, not that server) for the slime package because some of a stupid packaging error on my part and because the readme says that there is no general license for the package and that you should check all files individualy. When you do that you see that: doc/texinfo-tabulate.awk present.lisp swank-ecl.lisp swank-source-file-cache.lisp swank-source-path-parser.lisp swank.asd mkdist.sh test-all.sh test.sh have no license information. nregex.lisp has a (sort-of) licence without permission to distribute or anything. Could you clear these problems up? Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson|

15 30

[slime-devel] Strange startup behaviour
by Paul Lathrop 25 Oct '05

25 Oct '05

Hello all, I've been banging my head against this for a couple hours and haven't been able to figure out the problem, so I humbly ask for help or a pointer to the right place to ask: I'm attempting to run the current CVS SLIME with SBCL 0.9.5.50. When I hit M-x slime in emacs, compilation notes stream by, and then all action stops with the message: Lisp connection closed unexpectedly: connection broken by remote peer. Here's the weird part. If I start sbcl in a terminal and load up swank manually, connecting with M-x slime-connect from Emacs, everything works fine. I can't find anything enlightening in the *Messages* or *slime-events* buffers - it just quietly dies. Any ideas? --Paul

4 4

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 23 Oct '05

23 Oct '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.798 slime/ChangeLog:1.801 --- slime/ChangeLog:1.798 Fri Oct 21 10:08:24 2005 +++ slime/ChangeLog Sun Oct 23 10:53:00 2005 @@ -1,3 +1,26 @@ +2005-10-23 Stefan Kamphausen <skampi(a)gmx.net> + + * slime.el (slime-repl-history-size, slime-repl-history-file): Use + defcustom to declare the variables. + +2005-10-23 Gabor Melis <mega(a)hotpop.com> + + * swank-backend.lisp (install-debugger-globally): new interface + function + + * swank.lisp (install-debugger): call install-debugger-globally + + * swank-sbcl.lisp (install-debugger-globally): set + sb-ext:*invoke-debugger-hook* too + +2005-10-23 Helmut Eller <heller(a)common-lisp.net> + + * swank-sbcl.lisp (make-stream-interactive): Spawn a thread to + flush interactive streams in reasonably short intervals. + Remove the old backward-compatible threading implementation. + + * swank.lisp (package-string-for-prompt): Respect *print-case*. + 2005-10-21 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-start-swank-server): Avoid comint-send-input

1 0

[slime-devel] sbcl threads and specials
by Gábor Melis 23 Oct '05

23 Oct '05

The behaviour of SBCL's threads is about to be changed wrt specials. Threads shall no longer inherit the values of specials from the parent. It will be quite similar to other threaded lisps in this regard. Light testing shows that everything works fine except typing (sb-thread:make-thread (lambda () (break))) at the repl does not bring up the debugger anymore. It's because install-debugger in swank.lisp does not set the *invoke-debugger-hook*: (setq sb-ext:*invoke-debugger-hook* #'swank-debugger-hook) Until now the value of *invoke-debugger-hook* established by a let binding was inherited by threads, but that's no longer be the case. Let me know if there are other problems lurking behind the surface with the new scheme. Cheers, Gábor

3 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel