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

[slime-devel] contrib/slime-compiler-notes-tree.el also noted to not work
by wgl 24 Feb '09

24 Feb '09

Howdy: I too am seeing the problem with notes-tree. Is it as simple as renaming the file locally to get it to work? --wgl--

2 1

[slime-devel] New Aquamacs and Slime
by Marco Antoniotti 23 Feb '09

23 Feb '09

Hi I just upgraded Aquamacs and it looks like slime is not bundled anymore... (I thought it was). Is that the case? Cheers -- Marco Antoniotti

2 1

[slime-devel] Daily ChangeLog diff
by Helmut Eller 22 Feb '09

22 Feb '09

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.175 slime/contrib/ChangeLog:1.176 --- slime/contrib/ChangeLog:1.175 Tue Feb 17 09:03:46 2009 +++ slime/contrib/ChangeLog Sat Feb 21 19:05:21 2009 @@ -1,3 +1,10 @@ +2009-02-21 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime-package-fu.el: Removed misplaced comma, deleted some + end-of-line whitespace, added newline to the end of the file. + + Patch by Robert Brown. + 2009-02-17 Helmut Eller <heller(a)common-lisp.net> * slime-repl.el (slime-repl-connected-hook-function): Bind

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 20 Feb '09

20 Feb '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1678 slime/ChangeLog:1.1682 --- slime/ChangeLog:1.1678 Wed Feb 11 20:55:01 2009 +++ slime/ChangeLog Sat Feb 14 17:01:52 2009 @@ -1,3 +1,30 @@ +2009-02-14 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-reader-conditionals-regexp): New variable. Taken + from `slime-forward-reader-conditional'. + (slime-pretty-package-name): Fix modeline display for buffer + containing forms like (in-package "#+foo :A #-foo :B"). Also do + not call `read' on the name; the function does not need to return + a symbol, and `read' may choke on non-elisp syntax. + +2009-02-14 Helmut Eller <heller(a)common-lisp.net> + + Don't signal conditions in interrupt handler to + avoid problems with naive code like + (handler-case foo (condition bar)) + + * swank-backend.lisp (*interrupt-queued-handler*): Use a dynamic + variable instead. + (slime-interrupt-queued): Deleted. + * swank-cmucl.lisp, swank.lisp: Ditto. + +2009-02-14 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-restart-or-init-modeline-update-timer): Don't + run the timer repeatedly. + (slime-change-directory): Also change the directory in the + connection-buffer. + 2009-02-11 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el (slime-current-tlf, slime-current-form-path): New Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.173 slime/contrib/ChangeLog:1.174 --- slime/contrib/ChangeLog:1.173 Mon Feb 2 18:55:36 2009 +++ slime/contrib/ChangeLog Sat Feb 14 12:59:32 2009 @@ -1,3 +1,7 @@ +2009-02-14 Helmut Eller <heller(a)common-lisp.net> + + * swank.rb: New file. + 2009-02-02 Tobias C. Rittweiler <tcr(a)freebits.de> * swank-arglists.lisp (arglist-for-echo-area): Bleh, can't use

2 3

[slime-devel] SBCL 10.0.22 + latest SLIME = broken?
by Frank Shearar 18 Feb '09

18 Feb '09

Hi everyone, I'd found out about the issues around SBCL, SLIME and Windows. I thought perhaps I could just update my SLIME and perhaps some kind soul would have made the pain go away :). So yesterday I updated to the latest cvs version, deleted my ~/.slime/fasl/ directory, and started up SLIME. SLIME told me all the files it was recompiling, and gave me a REPL. Great. Then I tried to evaluate (+ 1 2), and got... nothing. Curious, I hit M-X slime again, said "no" to starting up another inferior-lisp, and SLIME started vomiting forth enormous amounts of stuff. The attachment shows the first few hundred lines of output. The second connection attempt starts at line 234, with this: CL-USER> (+ 1 2) (progn (load "c:/bin/emacs/site-lisp/slime/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init")) (funcall (read-from-string "swank:start-server") "c:/DOCUME~1/FrankS/LOCALS~1/Temp/slime.2444" :coding-system "iso-latin-1-unix")) ;; swank:close-connection: end of file on #<SB-SYS:FD-STREAM for "a socket" {247C9DA9}> Any idea what's going on? I figure that my system _used_ to be correctly set up, because it just worked (modulo the HANDLE-LISTEN issue). frank

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 18 Feb '09

18 Feb '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1682 slime/ChangeLog:1.1683 --- slime/ChangeLog:1.1682 Sat Feb 14 17:01:52 2009 +++ slime/ChangeLog Tue Feb 17 09:03:41 2009 @@ -1,3 +1,11 @@ +2009-02-17 Helmut Eller <heller(a)common-lisp.net> + + * swank.lisp (dispatch-event [:emacs-rex]): Reply a :invalid-rpc + message if the specified thread doesn't exist. + * slime.el (slime-dispatch-event): Handle :invalid-rpc. + (slime-init-connection-state): Bind slime-current-thread + to avoid problems with dead threads. + 2009-02-14 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el (slime-reader-conditionals-regexp): New variable. Taken Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.174 slime/contrib/ChangeLog:1.175 --- slime/contrib/ChangeLog:1.174 Sat Feb 14 12:59:32 2009 +++ slime/contrib/ChangeLog Tue Feb 17 09:03:46 2009 @@ -1,3 +1,8 @@ +2009-02-17 Helmut Eller <heller(a)common-lisp.net> + + * slime-repl.el (slime-repl-connected-hook-function): Bind + slime-current-thread to avoid problems with killed threads. + 2009-02-14 Helmut Eller <heller(a)common-lisp.net> * swank.rb: New file.

1 0

Re: [slime-devel] slime & sbcl event-loop issues
by xristos 16 Feb '09

16 Feb '09

Helmut, The point was calling things that register handlers from the repl which means the repl thread on :spawn mode. If i spawn another thread to call serve-event, my callbacks will never get called. Anyway, this is irrelevant now as fd-handler works. Something else: With slime current from cvs multiple repls in the same image don't seem to work. If i start swank with swank:create-server :port 6666 :dont-close t, and then connect with slime-connect only the first connection creates a repl. Subsequent ones do nothing (this used to work in the past). Also, doing slime-open-listener and including slime-mrepl creates a new listener but 1) slime-presentations do not work in the listener 2) I can only create at most 1 new listener 3) If i press enter on the listener i get: end of file on #<SB-IMPL::STRING-INPUT-STREAM {11A83009}> [Condition of type END-OF-FILE] Restarts: 0: [TERMINATE-THREAD] Terminate this thread (#<THREAD "swank- listener-thread" RUNNING {11A75EA9}>

1 0

Re: [slime-devel] slime & sbcl event-loop issues
by xristos 16 Feb '09

16 Feb '09

Ok problem solved, mostly. I updated slime from cvs and swank :fd-handler works now without me calling serve-event at all. Chris

1 0

[slime-devel] slime & sbcl event-loop issues
by xristos 15 Feb '09

15 Feb '09

I am trying to use serve-event to interactively monitor network protocols but i'm facing some issues when trying to work on the slime repl: 1) On threaded sbcl + :spawn swank comm style, serve-event does not run at all on the repl thread (the thread seems to be blocked on a call to condition-wait, in receive-if/swank-sbcl.lisp) I tried modifying receive-if so that it serves all pending events before acquiring the lock but i guess this could prove to be problematic. 2) Also tried scheduling a timer to interrupt *current-thread* (repl thread) and run serve-all-events periodically which works but i guess this is even worse than 1) and could explode pretty easy. 3) Using :fd-handler (and therefore a single thread) it seems that slime completely takes over the event loop and does not allow other handlers to run unless there is input coming from the repl. (Blocking on read-sequence ?) I could give up :spawn and work with :fd-handler comm style, if slime would let other handlers run and not block without configurable timeout at least. Is this feasible ? Where would one start looking in order to implement it ? Chris

2 3

[slime-devel] problem with debug-source-f[or|ro]m
by Vsevolod 13 Feb '09

13 Feb '09

Hi guys! I'm debugging a problem with slime startup on Windows, which symptom is this message on M-x slime: > Symbol "DEBUG-SOURCE-FROM" not found in the SB-DI package. > Curiously, when I skimmed through SBCL code, I didn't find any debug-source-fROm function, but have found debug-source-fORm. And in the slime sources the two even may be encountered side-by-side. I wonder, is it a coincidence or a typo, leading to a bug? Other unrelated question I've remembered. When I try to evaluate something in debugger process (with e <expr>), the slime connection dies (SBCL 1.0.20, Slime 2008-10-23, Debian GNU/Linux Etch). By chance, a common problem with a well-known solution? Thanks, Vsevolod

2 2