December 2008 - slime-devel - mailman3.common-lisp.net

[slime-devel] Slime with SBCL 1.0.22 on windows ; pipelined request... (swank:listener-eval "d
by Rayne 24 Dec '08

24 Dec '08

I installed slime, and SBCL for windows, and it works fine, except for the REPL. Everything works great until I do something to cause an error, when I do, the debugger fires and gives me my options, and no matter which one I choose, nothing happens. The CL-USER> prompt doesn't come back, it just hangs up, and any thing I type results in it saying "; pipelined request... (swank:listener-eval "d". Is there any way to fix this? This really sucks. I'm sure it's something to do with SBCL because the windows port is experimental, just shooting at the chance of there being a fix for it. Thanks -Rayne

5 5

[slime-devel] Hide REPL
by kogu 24 Dec '08

24 Dec '08

Hi, I am using Slime/Emacs on Windows. I have a dual monitor setup. So I create a new frame, move that to the second monitor, and set that to the Slime REPL buffer. Now in my main monitor, I have the code visible. When I run a function in the main window, the window is split in half with code and REPL showing. I want to stop this behavior of automatically splitting the window. The REPL on the other frame updates, so that's not a problem. So when I run a function (C-M-x), I don't want the window to split. Can anyone please help me with this? Thanks

4 3

[slime-devel] Daily ChangeLog diff
by Helmut Eller 24 Dec '08

24 Dec '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1597 slime/ChangeLog:1.1600 --- slime/ChangeLog:1.1597 Tue Dec 9 07:48:20 2008 +++ slime/ChangeLog Tue Dec 23 08:33:11 2008 @@ -1,3 +1,24 @@ +2008-12-23 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-run-mode-hooks): Wrapper for Emacs21. + (slime-repl-mode): Use it. + Reported by Peter Denno. + +2008-12-23 Sven Van Caekenberghe <sven(a)beta9.be> + + * swank.lisp (connection): Add a slot to store the + auto-flush-thread. + (cleanup-connection-threads): Also kill the auto-flush-thread. + + (stop-server): list-threads returns the thread name in second + position and not in first position. + +2008-12-23 Willem Broekema <metawilm(a)gmail.com> + + * slime.el (sldb-insert-restarts): Make the space before each + restart also propertized, consistent with how each line in the + backtrace is fully sensitive. + 2008-12-09 Helmut Eller <heller(a)common-lisp.net> Reset the stream column to 0 after eval requests.

1 0

[slime-devel] run-mode-hooks and emacs < version 22
by Peter Denno 23 Dec '08

23 Dec '08

Hi, I've had problems starting lisps (lw, sbcl) with emacs v21. Apparently, emacs versions before v22 do not define run-mode-hooks. But slime.el (CVS head) contains: (run-mode-hooks 'slime-repl-mode-hook) This would be better as: (if (fboundp 'run-mode-hooks) (run-mode-hooks 'slime-repl-mode-hook) (run-hooks 'slime-repl-mode-hook))) -- Best regards, - Peter

2 1

[slime-devel] auto-flush-thread cleanup and stop-server fix
by Sven Van Caekenberghe 23 Dec '08

23 Dec '08

Hi, While trying to use SLIME/SWANK to repeatedly connect/disconnect to/ from a remote long running server image I encountered some problems that I tried to fix. The server image is LispWorks 5.1.1 on Intel (Linux & Mac OS X), the client is Emacs 23 on Mac OS X 10.5.5 Intel, SLIME/SWANK the current CVS head. The first problem is that, in my situation, when running SWANK manually with (swank:create-server :dont-close t) and connecting/ disconnecting manually from SLIME, the auto-flush-thread was not cleaned up. Doing this multiple times gave me multiple defunct auto- flush-threads. Maybe this only happens on LispWorks, I don't know. I fixed this by adding an auto-flush-thread slot to the connect structure, setting this slot to the auto-flush-thread in open-streams and finally adding it to the thread list in cleanup-connection- threads. This seems to fix my problem in my situation. Is this an acceptable patch ? Also, calling stop-server with an integer port number didn't work. The problem was that list-threads returns the thread/process name in second position and not in first position (where the ID is). I included a diff below. If you want the patch any other way, just ask. HTH, Sven -- Sven Van Caekenberghe - mailto:sven@beta9.be Beta Nine - software engineering - http://www.beta9.be .Mac - svc(a)mac.com - http://homepage.mac.com/svc "Lisp isn't a language, it's a building material." - Alan Kay [sven@voyager:~/apps/slime]$ cvs diff -u swank.lisp Index: swank.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank.lisp,v retrieving revision 1.612 diff -u -r1.612 swank.lisp --- swank.lisp 9 Dec 2008 07:48:20 -0000 1.612 +++ swank.lisp 9 Dec 2008 10:48:08 -0000 @@ -241,6 +241,7 @@ reader-thread control-thread repl-thread + auto-flush-thread ;; Callback functions: ;; (SERVE-REQUESTS <this-connection>) serves all pending requests ;; from Emacs. @@ -762,7 +763,7 @@ (let ((thread-position (position-if (lambda (x) - (string-equal (first x) + (string-equal (second x) (concatenate 'string "Swank " (princ-to-string port)))) (list-threads)))) @@ -865,8 +866,9 @@ (repl-results (make-output-stream-for-target connection :repl-result))) (when (eq (connection.communication-style connection) :spawn) - (spawn (lambda () (auto-flush-loop out)) - :name "auto-flush-thread")) + (setf (connection.auto-flush-thread connection) + (spawn (lambda () (auto-flush-loop out)) + :name "auto-flush-thread"))) (values dedicated-output in out io repl-results))) ;; FIXME: if wait-for-event aborts the event will stay in the queue forever. @@ -1197,7 +1199,8 @@ (defun cleanup-connection-threads (connection) (let ((threads (list (connection.repl-thread connection) (connection.reader-thread connection) - (connection.control-thread connection)))) + (connection.control-thread connection) + (connection.auto-flush-thread connection)))) (dolist (thread threads) (when (and thread (thread-alive-p thread)

2 1

[slime-devel] restart lines fully propertized
by Willem Broekema 23 Dec '08

23 Dec '08

This small patch makes the space before each restart also propertized, consistent with how each line in the backtrace is fully sensitive. - Willem --- slime.el 5 Dec 2008 20:01:54 -0000 1.1070 +++ slime.el 6 Dec 2008 10:26:19 -0000 @@ -6930,12 +6930,11 @@ RESTARTS should be alist ((NAME DESCRIPTION) ...)." (loop for (name string) in restarts for number from 0 do - (insert " ") (slime-insert-propertized `(,@nil restart-number ,number sldb-default-action sldb-invoke-restart mouse-face highlight) - (in-sldb-face restart-number (number-to-string number)) + " " (in-sldb-face restart-number (number-to-string number)) ": [" (in-sldb-face restart-type name) "] " (in-sldb-face restart string)) (insert "\n")))

2 1

[slime-devel] Aquamacs/SLIME on Intel does not finish asdf load
by jcm＠sdf.lonestar.org 19 Dec '08

19 Dec '08

This problem does not have an actual error message in the REPL, so it's starting to frustrate me a bit. Loading a couple of large projects from the terminal/REPL works fine, but doing the same operation from SLIME stops, without an error, and with an unresponsive REPL. It never gives an error, or returns control to the prompt. Sometimes the cpu is pegged at 98+% on the sbcl process. ; registering #<SYSTEM :CHUNGA {12B70199}> as CHUNGA ; loading system definition from ; /Users/jonathon/.sbcl/systems/cl-base64.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM CL-BASE64 {132F7299}> as CL-BASE64 ; registering #<SYSTEM CL-BASE64-TESTS {1343A3A9}> as CL-BASE64-TESTS ; loading system definition from /Users/jonathon/.sbcl/systems/puri.asd ; into #<PACKAGE "ASDF0"> ; registering #<SYSTEM PURI {136D4251}> as PURI ; registering #<SYSTEM PURI-TESTS {13823489}> as PURI-TESTS ; loading system definition from ; /Users/jonathon/.sbcl/systems/cl-ppcre.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :CL-PPCRE {128692F1}> as CL-PPCRE CL-USER> 0

3 5

[slime-devel] Daily ChangeLog diff
by Helmut Eller 10 Dec '08

10 Dec '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1593 slime/ChangeLog:1.1597 --- slime/ChangeLog:1.1593 Sun Dec 7 12:25:38 2008 +++ slime/ChangeLog Tue Dec 9 07:48:20 2008 @@ -1,9 +1,39 @@ +2008-12-09 Helmut Eller <heller(a)common-lisp.net> + + Reset the stream column to 0 after eval requests. + + * swank.lisp (interactive-eval, eval-region): Use FRESH-LINE + to reset the stream column. + * slime.el (test repl-test): Adjust test accordingly. + +2008-12-09 Helmut Eller <heller(a)common-lisp.net> + + Be a bit more careful when computing the toplevel restart. + + * swank.lisp (throw-to-toplevel): Test *sldb-quit-restart* for + nilness. + * sldb-quit (sldb-quit): Show the returned value in brackets. + +2008-12-09 Helmut Eller <heller(a)common-lisp.net> + + Make the modeline a bit shorter. + + * slime.el (slime-compute-modeline-string): Remove PKG: and CON: + to save space. + (slime-compute-modeline-connection-state): Don't include zeros. + +2008-12-09 David Reitter <david.reitter(a)gmail.com> + + * slime.el (slime-repl-mode): Use `run-mode-hooks' rather than + just `run-hooks'. That way, after-change-major-mode-hook is + called automatically. + 2008-12-07 Nikodemus Siivola <nikodemus(a)random-state.net> * slime.el (slime-qualify-cl-symbol-name): Clean up the package name using `slime-pretty-package-name', so that packages named with strings are not left with the extra doublequotes. - + 2008-12-05 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el (slime-macroexpansion-minor-mode-map): Bind keybindings Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.142 slime/contrib/ChangeLog:1.143 --- slime/contrib/ChangeLog:1.142 Sat Nov 29 11:12:39 2008 +++ slime/contrib/ChangeLog Tue Dec 9 18:29:06 2008 @@ -1,3 +1,10 @@ +2008-12-09 Helmut Eller <heller(a)common-lisp.net> + + * swank-kawa.scm (mif): Avoid assignments because that triggers a + bug/regression in the compiler. + (getpid): Don't use the -n with echo. It's not standard and also + not needed here. + 2008-11-29 Tobias C. Rittweiler <tcr(a)freebits.de> * slime-package-fu.el (slime-goto-package-source-definition):

1 0

[slime-devel] problems with kawa + slime
by Sampo Vuori 09 Dec '08

09 Dec '08

Hi, It's great to see some support for kawa in slime.. I wanted to give it a go today but ran in a few showstoppers. With the latest kawa compiler I ran into an error which might be a compiler bug, when issuing the compile command: (compile-file "swank-kawa.scm" "swank-kawa") I get a stack trace: java.lang.Error: popType called with empty stack swank$Mnkawa.dispatchEvents(java.net.Socket)java.lang.Object at gnu.bytecode.CodeAttr.popType(CodeAttr.java:321) at gnu.bytecode.CodeAttr.emitStore(CodeAttr.java:1204) at gnu.expr.SetExp.compile(SetExp.java:279) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileWithPosition(Expression.java:133) at gnu.expr.IfExp.compile(IfExp.java:105) at gnu.expr.IfExp.compile(IfExp.java:41) at gnu.expr.Expression.compileWithPosition(Expression.java:133) at gnu.expr.BeginExp.compile(BeginExp.java:142) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compile(Expression.java:179) at gnu.expr.SetExp.compile(SetExp.java:273) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileWithPosition(Expression.java:133) at gnu.expr.IfExp.compile(IfExp.java:105) at gnu.expr.IfExp.compile(IfExp.java:41) at gnu.expr.Expression.compileWithPosition(Expression.java:133) at gnu.expr.BeginExp.compile(BeginExp.java:142) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compile(Expression.java:179) at gnu.expr.SetExp.compile(SetExp.java:273) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileWithPosition(Expression.java:133) at gnu.expr.IfExp.compile(IfExp.java:105) at gnu.expr.IfExp.compile(IfExp.java:41) at gnu.expr.Expression.compileWithPosition(Expression.java:133) at gnu.expr.BeginExp.compile(BeginExp.java:142) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compile(Expression.java:179) at gnu.expr.SetExp.compile(SetExp.java:273) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileWithPosition(Expression.java:133) at gnu.expr.IfExp.compile(IfExp.java:105) at gnu.expr.IfExp.compile(IfExp.java:41) at gnu.expr.Expression.compileWithPosition(Expression.java:133) at gnu.expr.BeginExp.compile(BeginExp.java:142) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.expr.LetExp.compile(LetExp.java:190) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:145) at gnu.expr.LambdaExp.compileBody(LambdaExp.java:1600) at gnu.expr.LambdaExp.compileAsMethod(LambdaExp.java:1577) at gnu.expr.LambdaExp.compileSetField(LambdaExp.java:640) at gnu.expr.LambdaExp.compile(LambdaExp.java:732) at gnu.expr.Expression.compile(Expression.java:179) at gnu.expr.SetExp.compile(SetExp.java:273) at gnu.expr.Expression.compileNotePosition(Expression.java:159) at gnu.expr.Expression.compileWithPosition(Expression.java:130) at gnu.kawa.functions.AppendValues.compile(AppendValues.java:51) at gnu.expr.ApplyExp.compile(ApplyExp.java:171) at gnu.expr.ApplyExp.compile(ApplyExp.java:110) at gnu.expr.Expression.compileWithPosition(Expression.java:148) at gnu.expr.LambdaExp.compileBody(LambdaExp.java:1600) at gnu.expr.Compilation.generateBytecode(Compilation.java:2010) at gnu.expr.Compilation.process(Compilation.java:1884) at gnu.expr.Compilation.compileToArchive(Compilation.java:988) at kawa.lib.system.compileFile(system.scm:93) at atInteractiveLevel$1.run(stdin) at gnu.expr.ModuleExp.evalModule(ModuleExp.java:293) at kawa.Shell.run(Shell.java:273) at kawa.Shell.run(Shell.java:184) at kawa.Shell.run(Shell.java:165) at kawa.repl.main(repl.java:864) After going back a few versions (to revision 6150) the swank-kawa compiles but I get the following error when starting slime in emacs: #|kawa:2|# connection: Socket[addr=/127.0.0.1,port=50431,localport=50430] listener: Thread[swank-listener,5,main] 1867624887 chan@11711970 #<environment user> attaching: -n 10332 20 attaching2: com.sun.jdi.ProcessAttach (defaults: pid=, timeout=) {pid=pid=-n 10332, timeout=timeout=20} closing socket: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=50430] Exception in thread "swank" java.lang.Error: mcase failed tmp (chan@1c4a1bda (error "java.io.IOException: Invalid process identifier" "IOException" ("com.sun.tools.jdi.ProcessAttachingConnector.attach(ProcessAttachingConnector.java:86)" "swank$Mnkawa.attach(swank-kawa.scm:1566)" "swank$Mnkawa.vmAttach(swank-kawa.scm:1551)" "swank$Mnkawa.vmMonitor(swank-kawa.scm:1157)" "swank$Mnkawa.apply1(swank-kawa.scm:1155)" "gnu.expr.ModuleBody.applyN(ModuleBody.java:207)" "swank$Mnkawa.applyN(swank-kawa.scm:1972)" "gnu.expr.ModuleMethod.applyN(ModuleMethod.java:213)" "gnu.kawa.functions.ApplyToArgs.applyN(ApplyToArgs.java:214)" "gnu.mapping.ProcedureN.apply2(ProcedureN.java:39)" "swank$Mnkawa$frame33.lambda56(swank-kawa.scm:1789)" "swank$Mnkawa$frame33.apply1(swank-kawa.scm:1787)" "gnu.expr.ModuleBody.applyN(ModuleBody.java:207)" "gnu.expr.ModuleMethod.applyN(ModuleMethod.java:213)" "gnu.kawa.functions.ApplyToArgs.applyN(ApplyToArgs.java:214)" "gnu.mapping.ProcedureN.apply2(ProcedureN.java:39)" "swank$Mnkawa$frame32.lambda55(swank-kawa.scm:1780)" "swank$Mnkawa$frame32.apply0(swank-kawa.scm:1780)" "gnu.expr.ModuleMethod.apply0(ModuleMethod.java:183)" "runnable.run(swank-kawa.scm:1802)" "java.lang.Thread.run(Thread.java:637)"))) at swank$Mnkawa.ferror$V(swank-kawa.scm:870) at swank$Mnkawa.dispatchEvents(swank-kawa.scm:367) at swank$Mnkawa.setupServer(swank-kawa.scm:323) at swank$Mnkawa$frame.lambda2(swank-kawa.scm:315) at swank$Mnkawa$frame.apply0(swank-kawa.scm:315) at gnu.expr.ModuleMethod.apply0(ModuleMethod.java:183) at runnable.run(swank-kawa.scm:1802) at java.lang.Thread.run(Thread.java:637) Any ideas how to fix these? (Running on OS X Leopard, Java 1.6.0_07) Thanks in advance - Sampo

2 1

[slime-devel] Daily ChangeLog diff
by Helmut Eller 08 Dec '08

08 Dec '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1592 slime/ChangeLog:1.1593 --- slime/ChangeLog:1.1592 Fri Dec 5 20:01:54 2008 +++ slime/ChangeLog Sun Dec 7 12:25:38 2008 @@ -1,3 +1,9 @@ +2008-12-07 Nikodemus Siivola <nikodemus(a)random-state.net> + + * slime.el (slime-qualify-cl-symbol-name): Clean up the package + name using `slime-pretty-package-name', so that packages named with + strings are not left with the extra doublequotes. + 2008-12-05 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el (slime-macroexpansion-minor-mode-map): Bind keybindings

1 0

[slime-devel] Problems with slime using sbcl on winXP (emacsW32)
by Matthew D. Swank 06 Dec '08

06 Dec '08

Starting in late September, whenever I try to exit out of the debugger the repl prompt doesn't come back. Example: *slime-repl sbcl* CL-USER> o *sldb sbcl/0* The variable O is unbound. [Condition of type UNBOUND-VARIABLE] Restarts: 0: [RETRY] Retry SLIME REPL evaluation request. 1: [ABORT] Return to SLIME's top level. <-----------pick this one 2: [CLOSE-CONNECTION] Close SLIME connection 3: [ABORT] Exit debugger, returning to top level. The repl buffer comes back with no prompt, and all further requests are pipelined. This does not happen in clisp. Some other info: *slime-events* (:emacs-rex (swank:listener-eval "o\n") "COMMON-LISP-USER" :repl-thread 14) (:debug 0 1 ("The variable O is unbound." " [Condition of type UNBOUND-VARIABLE]" nil) (("RETRY" "Retry SLIME REPL evaluation request.") ("ABORT" "Return to SLIME's top level.") ("CLOSE-CONNECTION" "Close SLIME connection") ("ABORT" "Exit debugger, returning to top level.")) ((0 "(SB-INT:SIMPLE-EVAL-IN-LEXENV O #<NULL-LEXENV>)") (1 "(SWANK::EVAL-REGION \"o\\n\")") (2 "((LAMBDA ()))") (3 "(SWANK::TRACK-PACKAGE #<CLOSURE (LAMBDA #) {25B5C3E5}>)") (4 "(SWANK::CALL-WITH-RETRY-RESTART \"Retry SLIME REPL evaluation request.\" #<CLOSURE (LAMBDA #) {25B5C375}>)") (5 "(SWANK::CALL-WITH-BUFFER-SYNTAX NIL #<CLOSURE (LAMBDA #) {25B5C35D}>)") (6 "(SWANK::REPL-EVAL \"o\\n\")") (7 "(SB-INT:SIMPLE-EVAL-IN-LEXENV (SWANK:LISTENER-EVAL \"o\\n\") #<NULL-LEXENV>)") (8 "(SWANK::EVAL-FOR-EMACS (SWANK:LISTENER-EVAL \"o\\n\") \"COMMON-LISP-USER\" 14)") (9 "(SWANK::PROCESS-REQUESTS NIL)") (10 "((LAMBDA ()))") (11 "((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {241035BD}>)") (12 "(SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {2401F269}> #<CLOSURE (LAMBDA #) {241035CD}>)") (13 "(SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {2401F269}> #<CLOSURE (LAMBDA #) {241035BD}>)") (14 "(SWANK::HANDLE-REQUESTS #<SWANK::CONNECTION {2401F269}> NIL)") (15 "((LAMBDA ()))") (16 "((LAMBDA (SWANK-BACKEND::HANDLER FUNCTION)) #<FUNCTION (LAMBDA #) {23DC867D}> #<CLOSURE (LAMBDA #) {24103555}>)") (17 "(SWANK::SIMPLE-SERVE-REQUESTS #<SWANK::CONNECTION {2401F269}>)") (18 "(SWANK::SERVE-CONNECTION #<SB-BSD-SOCKETS:INET-SOCKET descriptor -1 {23FB59F9}> NIL NIL :ISO-8859-1)") (19 "(SWANK::SETUP-SERVER 0 #<CLOSURE (LAMBDA #) {23F4527D}> NIL NIL :ISO-8859-1)")) (14)) (:debug-activate 0 1 nil) (:emacs-rex (swank:invoke-nth-restart-for-emacs 1 1) nil 0 15) (:return (:abort) 15) (:debug-return 0 1 nil) These are the current contribs I'm using: (require 'slime-fancy) (require 'slime-asdf) Just using straight socket for communication: swank:*communication-style* => nil Matt -- "You do not really understand something unless you can explain it to your grandmother." -- Albert Einstein.

3 7

[slime-devel] Prefix-Arg of slime-toggle-trace-fdefinition
by Tobias C. Rittweiler 06 Dec '08

06 Dec '08

Hi, is there a particular reason why C-u C-c C-t is not the default behaviour of C-c C-t? Perhaps it's better if C-c C-t always tries to look at the context, but then offers that choice to the user in a way that is correctable by the user. Say it prompts for (flet foo) for a local function. -T.

2 1

[slime-devel] Daily ChangeLog diff
by Helmut Eller 06 Dec '08

06 Dec '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1590 slime/ChangeLog:1.1592 --- slime/ChangeLog:1.1590 Tue Dec 2 22:00:41 2008 +++ slime/ChangeLog Fri Dec 5 20:01:54 2008 @@ -1,3 +1,17 @@ +2008-12-05 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-macroexpansion-minor-mode-map): Bind keybindings + of `undo' to `slime-macroexpansion-undo'. + (slime-show-macroexpansion): Renamed to + `slime-initialize-macroexpansion-buffer' + (slime-initialize-macroexpansion-buffer): Make sure that the user + can't undo past the initial insertion. + (slime-macroexpand-undo): New function. Tries to undo-only. + +2008-12-05 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-trace-query): SPEC argument can be a symbol. + 2008-12-02 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el (slime-compute-modeline-connection-state): Fix

1 0

[slime-devel] [PATCH] more reader cleanups
by Tobias C. Rittweiler 05 Dec '08

05 Dec '08

* make-d-macro-char.diff Currently, invoking MAKE-DISPATCH-MACRO-CHARACTER on a character that's already been made a dispatch macro character results in an error. All other implementations I tested, do not signal an error, but just override a possibly existing dispatch table. I think that's sensible, as the the CLHS entry for MAKE-D-M-CHAR says Exceptional Situations are None. * get-dtable-pair.diff The implementation for retrieving an entry from the dispatch tables is currently duplicated on all call sites. This patch introduces an explicit getter function. Also, in SET-DISPATCH-MACRO-CHARACTER the function argument was COERCED to a function (thus allowing literal lambda expressions), use %COERCE-TO-CALLABLE instead. * inline-assert-not-std-rt.diff Inline ASSERT-NOT-STANDARD-READTABLE, and MAKE-DISPATCH-CHAR-TABLE. * char-attr-table-type.diff Introduce an explicit type for character attributes (CHAR-ATTR), and rename the type ATTRIBUTE-TABLE to CHAR-ATTR-TABLE. * ref-cat-entry.diff Fix more FIXMES and code duplication by introducing a low-level getter REF-CAT-TABLE which is then used at the appropriate places. -T.

1 1

[slime-devel] Daily ChangeLog diff
by Helmut Eller 03 Dec '08

03 Dec '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1587 slime/ChangeLog:1.1590 --- slime/ChangeLog:1.1587 Sun Nov 23 22:11:36 2008 +++ slime/ChangeLog Tue Dec 2 22:00:41 2008 @@ -1,3 +1,23 @@ +2008-12-02 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-compute-modeline-connection-state): Fix + computation of debugged requests. + +2008-11-30 Gábor Melis <mega(a)retes.hu> + + * slime.el (slime-compute-modeline-connection-state): Print the + number of debugged requests if non-zero. + (slime-connection-state-as-string): Removed unused branches. + (slime-compute-connection-state): Removed :debugged branch making + most likely return :connected instead. + +2008-12-02 Tobias C. Rittweiler <tcr(a)freebits.de> + + Modeline wouldn't display {debugged..} after `slime-interrupt'. + + * slime.el (slime-debugged-connection-p): Can't rely on + `sldb-debugged-continuations' to be non-null in every SLDB buffer. + 2008-11-23 Helmut Eller <heller(a)common-lisp.net> `q' in temp buffers should only delete the window if it was newly

1 0

[slime-devel] [BUG] quitting from sldb after error in thread
by Tobias C. Rittweiler 03 Dec '08

03 Dec '08

On SBCL, evaluating (swank::spawn #'(lambda () (error "FOO"))) at the REPL, then pressing `q' in SLDB results in an invocation of (FIND-RESTART NIL) which is an error in itself. -T.

1 0

[slime-devel] Reincarnate "eval..."
by Gábor Melis 02 Dec '08

02 Dec '08

Running cvs HEAD I now realize that I grew to rely on checking the modeline of lisp buffers to see whether there are outstanding requests. Often, I start evalutations that take minutes or hours to finish and it's useful to have this at a glance without having to worry about missing when the return value is printed or having to check the running threads. The attached patch does not reinstate "eval...", instead it displays the number of outstanding requests like "CON:sbcl{3}" if it's greater than zero. Currently there is a loop through buffer-list, it that's a problem maybe there is a better way to arrange for the modeline to be updated using a global mode-line-format variable as a trigger to signal the change in connection-state that is to be recomputed in each slime buffer. The patch does not solve the minor problems caused by the use of run-with-idle-timer, namely that the modeline may not be updated if the status of the connection changes in the background while emacs is idle. Cheers, Gábor

3 3

[slime-devel] slime-undefmethod contrib
by Madhu 02 Dec '08

02 Dec '08

Attached is my first contrib submission. M-x slime-undefine-function does not help when you wish to remove a specific method. This contrib adds a new function slime-undefmethod. Invoking M-x slime-undefmethod with the point inside a defmethod definition in your source will find and remove the specific method. I've posted the code before on usenet, but felt it may be more useful if packaged up with slime. Comments welcome. -- Madhu

2 1

[slime-devel] Call stack when using Lisp debugger from sldb
by Raymond Toy 01 Dec '08

01 Dec '08

Sometimes when I'm in sldb, I want to use the actual Lisp debugger because sometimes it more convenient to have a real repl. Pressing B works nicely. Previously, however, I would be in the debugger, and the backtrace would be exactly what I expected, with the top of stack being exactly where the error occurred. Now, however, the actual error is some 10-20 frames away because there are lots of slime things in between. This is kind of nice too because now I can return to sldb, which I couldn't before. But this also means I now have to go hunt around for the real offending frame. Is there a way to the old behavior? Ray

3 5