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

[slime-devel] SWANK:LIST-THREADS
by Tobias C. Rittweiler 08 Aug '08

08 Aug '08

Hi, is there any intrinsic reason why LIST-THREADS stores the currently active threads in *THREAD-LIST*? Since we transmit the actual thread ids back to Emacs, we could simply use them to retrieve the thread objects, couldn't we? -T.

2 2

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 08 Aug '08

08 Aug '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1400 slime/ChangeLog:1.1406 --- slime/ChangeLog:1.1400 Wed Aug 6 15:51:39 2008 +++ slime/ChangeLog Thu Aug 7 13:07:22 2008 @@ -1,3 +1,64 @@ +2008-08-07 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-with-temp-buffer): By default, no longer inherit + the current connection. + +2008-08-07 Tobias C. Rittweiler <tcr(a)freebits.de> + + Previously, M-p at the REPL deleted the input if no match could be + found in the history. Now the input is untouched. + + * slime.el (slime-repl-history-replace): Ditch delete-at-end-p + argument. + (slime-repl-next-input, slime-repl-previous-input): Adapted. + (slime-repl-forward-input, slime-repl-backward-input): Ditto. + +2008-08-07 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-with-temp-buffer): Renamed from + slime-with-output-to-temp-buffer. Initialize the buffer local + buffer variables before and after running BODY, so that we don't + need the mode argument. + +2008-08-07 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (def-slime-test narrowing): Adapted to recent changes + of `slime-with-output-to-temp-buffer'. + +2008-08-07 Tobias C. Rittweiler <tcr(a)freebits.de> + + Mode-Line will now display a buffer's connection, and a buffer's + package. Furthermore, stale connections will also be indicated. + + * slime.el: (slime-update-modeline-package): Renamed to + `slime-extended-modeline'. + (slime-modeline-string), + (slime-modeline-connection-name), + (slime-modeline-connection-state): New variables. + (slime-update-modeline-package): Renamed to + `slime-compute-modeline-package'. + (slime-compute-modeline-connection): New. + (sime-compute-modeline-connection-state): New. + (slime-compute-modeline-string): New. + (slime-update-modeline-string): New. + (slime-shall-we-update-modeline-p): New. + (slime-update-modeline): New. Run periodically by idle timer. + + (slime-mode, slime-temp-buffer-mode): Install extended mode-line. + + (slime-stale-connection-p, slime-debugged-connection-p): New. + (slime-compute-connection-state): New. + (slime-connection-state-as-string): New. + (slime-state-name): Removed. + (slime-set-state): Removed. + + (slime-length>): Fix typecase. + +2008-08-07 Helmut Eller <heller(a)common-lisp.net> + + * swank-allegro.lisp, swank-cmucl.lisp, + swank-scl.lisp (receive-if): Periodically check for interrupts. + 2008-08-06 Nikodemus Siivola <nikodemus(a)random-state.net> * swank-sbcl.lisp (handle-notification-condition): resignal Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.115 slime/contrib/ChangeLog:1.117 --- slime/contrib/ChangeLog:1.115 Tue Aug 5 14:19:34 2008 +++ slime/contrib/ChangeLog Thu Aug 7 11:24:08 2008 @@ -1,3 +1,12 @@ +2008-08-07 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime-fancy.el: Add slime-mdot-fu and slime-package-fu. + +2008-08-07 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime-mdot-fu.el: Works for LET bindings now also. + (def-slime-test find-local-definitions.1): New test case. + 2008-08-05 Michael Weber <michaelw+slime(a)foldr.org> * slime-typeout-frame.el (slime-typeout-message-aux): prevent

1 0

[slime-devel] Slime-With-Temp-Buffer
by Tobias C. Rittweiler 07 Aug '08

07 Aug '08

Hi, slime-with-temp-buffer stores a connection buffer-locally by default even when it's not needed (*SLIME Description*, *SLIME Compiler-Notes*); Given that those connections can become stale, I'd rather have as few buffer store connections buffer-locally as possible, as it can result in confusing behaviour. Additionally, the disconnect test is subtly broken. Look into *Messages* after running the test suite, there's "cond: Connection closed" message resulting from the last use of (slime-inferior-process) in the test case. The test is implicitly run in a Compiler-Notes buffer whose connection becomes stale during the test. And this leaves Slime in a weird state, just run the test suite a second time. -T.

2 1

[slime-devel] sbcl: continual warnings about releasing threads
by okflo＠diesenbacher.net 07 Aug '08

07 Aug '08

Hi fabulous developers of slime, :) with updating slime by cvs today, my repl gets messed up by continual, never ending warnings: WARNING: Releasing #S(SB-THREAD:MUTEX :NAME NIL :%OWNER NIL :LUTEX #<unknown pointer object, widetag=#x5E {11B7911F}>), owned by another thread: NIL this is sbcl 1.0.18 with threads on mac os 10.5.4. best regards okflo

3 5

[slime-devel] slime-filename-translations usage
by Xavier Maillard 07 Aug '08

07 Aug '08

Hi, I have setup a remote host where I am building (slowly) several webapps using Common Lisp. As a GNU Emacs user, I am also using SLIME which makes all this fun work even funnier, thank you. I have a question with s-c-t. I have something like this in my local .emacs file: ;; Path translation (must have slime-tramp loaded) (push (slime-create-filename-translator :machine-instance "maillard.mobi" :remote-host "maillard.mobi" :username "xma") slime-filename-translations) Which, if I understand correctly should allow me to "kludge" emacs/slime and be able to send remote file in my local slime REPL. The problem is I do not understand how I should open the remote file. Do I need to do as usual via tramp or is there a trick not to type the long /ssh:.../ string ? Thank you -- Xavier Maillard

2 1

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 07 Aug '08

07 Aug '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1396 slime/ChangeLog:1.1400 --- slime/ChangeLog:1.1396 Tue Aug 5 14:19:33 2008 +++ slime/ChangeLog Wed Aug 6 15:51:39 2008 @@ -1,3 +1,39 @@ +2008-08-06 Nikodemus Siivola <nikodemus(a)random-state.net> + + * swank-sbcl.lisp (handle-notification-condition): resignal + warnings as-is before replacing with COMPILER-CONDITION so that + handlers higher up the stack can muffle them should they choose + to. This silences redefinition warnings for definitions inside + EVAL-WHEN :COMPILE-TOPLEVEL in newish SBCLs when compiling the + file for a second time. + (call-with-compilation-hooks): STYLE-WARNINGs are WARNINGs, and + don't need a separate handler. + +2008-08-06 Helmut Eller <heller(a)common-lisp.net> + + * swank-sbcl.lisp (short-backtrace): New function. + (thread-description): Use it. + + * slime.el (slime-show-apropos): Use lisp-syntax-table to make + M-. more useful. + +2008-08-06 Helmut Eller <heller(a)common-lisp.net> + + Queue interrupts in various places. + + * swank-backend.lisp (*pending-slime-interrupts*): New variable. + (check-slime-interrupts): New function. + + * swank-lispworks.lisp (receive-if): Use it. + + * swank-sbcl.lisp, swank-openmcl.lisp: Ditto. + + * swank.lisp (*slime-interrupts-enabled*): New variable. + (with-slime-interrupts, without-slime-interrupts): New macros. + (invoke-or-queue-interrupt): New function. + (interrupt-worker-thread, eval-for-emacs, swank-debugger-hook) + (debug-nth-thread, wait-for-event, read-from-emacs): Use them. + 2008-08-05 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-with-output-to-temp-buffer): Make sure that we

1 0

[slime-devel] Use of with-lock inside without-interrupts
by Martin Simmons 06 Aug '08

06 Aug '08

I see some new changes in swank-lispworks.lisp where mp:with-lock is used inside mp:without-interrupts. What is the purpose of that? It is wrong because it will lead to deadlock if the lock is held by another thread (you can't wait if you are inside without-interrupts). I suggest removing the without-interrupts because the lock does is better anyway. -- Martin Simmons LispWorks Ltd http://www.lispworks.com/

3 6

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 06 Aug '08

06 Aug '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1391 slime/ChangeLog:1.1396 --- slime/ChangeLog:1.1391 Mon Aug 4 17:38:07 2008 +++ slime/ChangeLog Tue Aug 5 14:19:33 2008 @@ -1,3 +1,26 @@ +2008-08-05 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-with-output-to-temp-buffer): Make sure that we + don't make the wrong buffer read-only. + + * swank-lispworks.lisp (make-stream-interactive): Run our own + thread to periodically flush streams instead of relying on + soft-force-output. + + * swank.lisp (encode-message): Inhibit interrupts + while writing the length and the body. + + * swank-backend.lisp (make-recursive-lock) + (call-with-recursive-lock-held): Deleted. Make the default locks + "recursive" instead. + (thread-id): Add a default implementation which works + with the default implementation of current-thread. + + * swank-gray.lisp (stream-write-string): New method. + + * swank-backend.lisp (*gray-stream-symbols*): Include + write-string. + 2008-08-04 Helmut Eller <heller(a)common-lisp.net> * swank-gray.lisp (slime-output-stream): Undo last change. Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.114 slime/contrib/ChangeLog:1.115 --- slime/contrib/ChangeLog:1.114 Mon Aug 4 16:25:57 2008 +++ slime/contrib/ChangeLog Tue Aug 5 14:19:34 2008 @@ -1,3 +1,13 @@ +2008-08-05 Michael Weber <michaelw+slime(a)foldr.org> + + * slime-typeout-frame.el (slime-typeout-message-aux): prevent + typeout messages from scribbling into any buffer which happens to + be in the typeout window + (slime-typeout-buffer): new function; changed buffer name to + "*SLIME Typeout*" + (slime-make-typeout-frame): use it + (slime-ensure-typeout-frame): ensure typeout buffer is visible + 2008-08-04 Adam Bozanich <adam.boz(a)gmail.com> * slime-asdf.el: Load swank-asdf.

1 0

[slime-devel] [PATCH] Prevent typeout messages to be scribbled into random buffers
by Michael Weber 05 Aug '08

05 Aug '08

Hi, the slime-typeout-frame contrib would happily scribble into any buffer which is current in the typeout window. Attached patch fixes this. As mentioned on IRC the typeout implementation probably could be done differently, but for the time being this patch at least fixes the immediate issues. Cheers, Michael

2 3

[slime-devel] Problem with slime+sbcl on osx
by Bhaskara Marthi 05 Aug '08

05 Aug '08

Hi all, I'm trying to set up slime+sbcl on my macbook. However, when I try to compile my code (which I've previously done successfully on slime+sbcl+ubuntu), the compilation process eventually stops, and I get an "Evaluation aborted" message in the minibuffer. Looking at inferior-lisp, it seems to have gone into an infinite loop about something (see below). Any suggestions? - Bhaskara * ; loading #P"/Users/bhaskara/bin/slime/swank-loader.lisp" ; loading #P"/Users/bhaskara/.slime/fasl/2008-08-04/sbcl-1.0.12-darwin-x86/swank-backend.fasl" ; loading #P"/Users/bhaskara/.slime/fasl/2008-08-04/sbcl-1.0.12-darwin-x86/swank-source-path-parser.fasl" ; loading #P"/Users/bhaskara/.slime/fasl/2008-08-04/sbcl-1.0.12-darwin-x86/swank-source-file-cache.fasl" ; loading #P"/Users/bhaskara/.slime/fasl/2008-08-04/sbcl-1.0.12-darwin-x86/swank-sbcl.fasl" STYLE-WARNING: redefining EMACS-INSPECT (#<BUILT-IN-CLASS T>) in DEFMETHOD ; loading #P"/Users/bhaskara/.slime/fasl/2008-08-04/sbcl-1.0.12-darwin-x86/swank-gray.fasl" STYLE-WARNING: implicitly creating new generic function STREAM-READ-CHAR-WILL-HANG-P ; loading #P"/Users/bhaskara/.slime/fasl/2008-08-04/sbcl-1.0.12-darwin-x86/swank.fasl" WARNING: These Swank interfaces are unimplemented: (ALL-THREADS CALLS-WHO DISASSEMBLE-FRAME FIND-THREAD INTERRUPT-THREAD RECEIVE RECEIVE-IF SEND SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN SPAWN THREAD-ID WHO-SPECIALIZES) ;; Swank started at port: 49393. 49393 * Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded. 0: (BACKTRACE 536870911 #<SYNONYM-STREAM :SYMBOL SB-SYS:*TTY* {124E21C9}>) 1: ((LAMBDA NIL)) 2: ((LAMBDA NIL)) 3: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #<CLOSURE (LAMBDA NIL) {124E22E5}>) 4: (SB-IMPL::ERROR-ERROR) 5: (SB-IMPL::INFINITE-ERROR-PROTECTOR) 6: (ERROR "~S not implementated") 7: (SWANK-BACKEND:THREAD-ID 0) 8: ((LAMBDA NIL)) 9: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL) {124E1BBD}>) 10: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {11746E71}> #<CLOSURE (LAMBDA NIL) {124E1BD5}>) 11: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {11746E71}> #<CLOSURE (LAMBDA NIL) {124E1BBD}>) 12: ((LAMBDA NIL)) 13: ((SB-PCL::FAST-METHOD STREAM-FINISH-OUTPUT (SWANK-BACKEND::SLIME-OUTPUT-STREAM)) #(3 NIL 2 NIL 5 NIL 1 NIL) #<unavailable argument> #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>) 14: (FINISH-OUTPUT #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>) 15: ((SB-PCL::FAST-METHOD STREAM-WRITE-CHAR (SWANK-BACKEND::SLIME-OUTPUT-STREAM T)) #(3 NIL 2 NIL 4 NIL 5 NIL) #<unavailable argument> #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}> #\K) 16: ((SB-PCL::FAST-METHOD STREAM-WRITE-STRING (FUNDAMENTAL-CHARACTER-OUTPUT-STREAM "#<...>" . "#<...>")) #<unused argument> #<unused argument> #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}> "((SB-PCL::FAST-METHOD STREAM-FINISH-OUTPUT (SWANK-BACKEND::SLIME-OUTPUT-STREAM)) #(3 NIL 2 NIL 5 NIL 1 NIL) #<unavailable argume" 0 128) 17: (WRITE-STRING "((SB-PCL::FAST-METHOD STREAM-FINISH-OUTPUT (SWANK-BACKEND::SLIME-OUTPUT-STREAM)) #(3 NIL 2 NIL 5 NIL 1 NIL) #<unavailable argume" #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}> :START 0 :END 128) 18: (SB-IMPL::%WRITE-STRING "((SB-PCL::FAST-METHOD STREAM-FINISH-OUTPUT (SWANK-BACKEND::SLIME-OUTPUT-STREAM)) #(3 NIL 2 NIL 5 NIL 1 NIL) #<unavailable argume" #<TWO-WAY-STREAM :INPUT-STREAM #<SWANK-BACKEND::SLIME-INPUT-STREAM {1182E251}> :OUTPUT-STREAM #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>> 0 128) 19: (WRITE-STRING "((SB-PCL::FAST-METHOD STREAM-FINISH-OUTPUT (SWANK-BACKEND::SLIME-OUTPUT-STREAM)) #(3 NIL 2 NIL 5 NIL 1 NIL) #<unavailable argume" #<TWO-WAY-STREAM :INPUT-STREAM #<SWANK-BACKEND::SLIME-INPUT-STREAM {1182E251}> :OUTPUT-STREAM #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>> :START 0 :END 128) 20: (SB-PRETTY::OUTPUT-PARTIAL-LINE #<SB-PRETTY:PRETTY-STREAM {124E0B21}>) 21: (SB-PRETTY::ENSURE-SPACE-IN-BUFFER #<SB-PRETTY:PRETTY-STREAM {124E0B21}> 2) 22: (SB-PRETTY::PRETTY-SOUT #<SB-PRETTY:PRETTY-STREAM {124E0B21}> "unavailable argument" #<unavailable argument> 20) 23: (SB-IMPL::%WRITE-STRING "unavailable argument" #<SB-PRETTY:PRETTY-STREAM {124E0B21}> 0 20) 24: (WRITE-STRING "unavailable argument" #<SB-PRETTY:PRETTY-STREAM {124E0B21}> :START 0 :END NIL) 25: ((FLET SB-IMPL::PRINT-DESCRIPTION)) 26: (SB-IMPL::%PRINT-UNREADABLE-OBJECT #<unavailable argument> #<SB-PRETTY:PRETTY-STREAM {124E0B21}> NIL NIL #<CLOSURE (LAMBDA NIL) {124E16AD}>) 27: (PRIN1 #<unavailable argument> #<SB-PRETTY:PRETTY-STREAM {124E0B21}>) 28: (SB-FORMAT::S-FORMAT-DIRECTIVE-INTERPRETER #<SB-PRETTY:PRETTY-STREAM {124E0B21}> #<~S> NIL #<unavailable argument> #<unavailable argument>) 29: (SB-FORMAT::INTERPRET-DIRECTIVE-LIST #<SB-PRETTY:PRETTY-STREAM {124E0B21}> (#<~S>) (#(3 NIL 2 NIL 5 NIL 1 NIL) #<unavailable argument> #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>) (#<unavailable argument> #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>)) 30: ((LABELS SB-FORMAT::DO-LOOP) (#(3 NIL 2 NIL 5 NIL 1 NIL) #<unavailable argument> #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>) (#<unavailable argument> #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>)) 31: (SB-FORMAT::{-FORMAT-DIRECTIVE-INTERPRETER #<SB-PRETTY:PRETTY-STREAM {124E0B21}> #<~{> (" " #<~_> #<~S> #<~}>) ((#(3 NIL 2 NIL 5 NIL 1 NIL) #<unavailable argument> #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>)) #<unavailable argument>) 32: (SB-FORMAT::INTERPRET-DIRECTIVE-LIST #<SB-PRETTY:PRETTY-STREAM {124E0B21}> (#<~{> " " #<~_> #<~S> #<~}>) ((#(3 NIL 2 NIL 5 NIL 1 NIL) #<unavailable argument> #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>)) ((#(3 NIL 2 NIL 5 NIL 1 NIL) #<unavailable argument> #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>))) 33: (SB-FORMAT::%FORMAT #<SB-PRETTY:PRETTY-STREAM {124E0B21}> "~{ ~_~S~}" ((#(3 NIL 2 NIL 5 NIL 1 NIL) #<unavailable argument> #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>)) ((#(3 NIL 2 NIL 5 NIL 1 NIL) #<unavailable argument> #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>))) 34: (FORMAT #<SB-PRETTY:PRETTY-STREAM {124E0B21}> "~{ ~_~S~}") 35: ((FLET #:WITH-PRETTY-STREAM-132) #<SB-PRETTY:PRETTY-STREAM {124E0B21}>) 36: (SB-DEBUG::PRINT-FRAME-CALL #<SB-DI::COMPILED-FRAME (SB-PCL::FAST-METHOD STREAM-FINISH-OUTPUT (SWANK-BACKEND::SLIME-OUTPUT-STREAM))> #<TWO-WAY-STREAM :INPUT-STREAM #<SWANK-BACKEND::SLIME-INPUT-STREAM {1182E251}> :OUTPUT-STREAM #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>>) 37: (BACKTRACE 536870911 #<TWO-WAY-STREAM :INPUT-STREAM #<SWANK-BACKEND::SLIME-INPUT-STREAM {1182E251}> :OUTPUT-STREAM #<SWANK-BACKEND::SLIME-OUTPUT-STREAM {11672799}>>) 38: ((LAMBDA NIL)) 39: ((LAMBDA NIL)) 40: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #<CLOSURE (LAMBDA NIL) {12444EA5}>) 41: (SB-IMPL::ERROR-ERROR) 42: (SB-IMPL::INFINITE-ERROR-PROTECTOR) 43: (ERROR "~S not implementated") << and so on >>

2 1