October 2005 - slime-devel - mailman3.common-lisp.net

[slime-devel] slime-apropos-package now sorts correctly
by Hoehle, Joerg-Cyril 20 Apr '07

20 Apr '07

Hi, slime-apropos-package now conforms to its specification and also sorts symbols printed with package prefix. I supply the patches as attachments in the hope that MS-Windows nor MS-Outlook will break the TAB and LF characters of the original diff. I hope this is fine. Regards, Jörg Höhle.

3 3

[slime-devel] comma shortcut doesn't work always
by Edi Weitz 31 Jan '06

31 Jan '06

Another minor glitch that I encountered is that the comma shortcut in the REPL doesn't always work. I can consistently reproduce it (GNU Emacs 21.3.50 and also 21.3 release) like this: 1. Make sure point is at the beginning of a REPL input line. 2. Split Emacs frame into two windows, one of them being the REPL the other one containing something else. 3. Hide REPL window with C-x 0. 4. Now type M-x slime. 5. Type the comma. At this point I'm not asked for a shortcut command in the minibuffer but the comma is simply entered into the REPL instead. Anybody else seeing this? Cheers, Edi.

10 25

Re: [slime-devel] Re: CLISP SLIME implementation breaks in CVS
by Bill_Clementson＠peoplesoft.com 21 Jan '06

21 Jan '06

Luke Gorrie <luke(a)bluetail.com> writes: > Bill_Clementson(a)peoplesoft.com writes: > > > My previous SLIME installation was a CVS install from 4/18. I've just taken > > the latest CVS install and the CLISP SLIME implementation (under Windows) > > breaks. Here is the error: > > > > COERCE: #<MACRO #<COMPILED-CLOSURE SWANK::DEFSLIMEFUN>> cannot be coerced > > to type FUNCTION > > [Condition of type SIMPLE-TYPE-ERROR] > > I can reproduce this but I've no idea what is causing it. It /looks/ > like someone is trying to call defslimefun as a function rather than a > macro, but I don't see where it could happen -- the macro is declared > at the top of the only file that refers to it. > > I did fix a different but similar problem that I got under CLISP. It > seems like I had to swap the order of a couple of macros, one of which > expanded into into code that calls the other, but that surely can't be > the reason. > > > Backtrace: > > 0: EVAL frame for form (SWANK:CREATE-SWANK-SERVER 4007) > > Mine actually gives an empty backtrace (!). I fixed the Elisp-side to > handle that incase it helps someone more CLISP-savvy find the problem. Has anybody had any luck in finding the source of this problem? CLISP still breaks for me in the latest CVS. I have had a look at all of the DEFSLIMEFUN's that were modified since 4/18 (the previous CVS version that I had which was working ok with CLISP) and haven't found any obvious clues. Any suggestions on how I might debug this issue as it occurs at startup during the slime-connect processing in Emacs (after CLISP has started up successfully)? - Bill

5 6

[slime-devel] Installing slime for clisp 2.35 - Error
by Surendra Singhi 10 Jan '06

10 Jan '06

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 Doing 'continue', doesn't starts the slime repl, nor does selecting any of the restarts help. But, the inferior lisp buffer shows a lisp prompt, which can be used. What should I do to get over this problem? The slime related contents of my init file are: (load-library "inf-lisp") (setq inferior-lisp-program "C:\\clisp-2.35\\clisp.exe -I -m 256mb") (add-hook 'inferior-lisp-mode-hook (lambda () (inferior-slime-mode t))) (require 'timer) (require 'slime) (slime-setup) Thanks. -- 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

5 8

[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 30 Oct '05

30 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