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

[slime-devel] [RfC] SPC vs. RET in Xref Buffers
by Tobias C. Rittweiler 10 Aug '08

10 Aug '08

Hi, In XREF buffers, pressing RET will open the definition at point in the buffer where you originally issued the xref command, but let the XREF buffer open and let point still be in there. Pressing, SPACE will bring one to the definition at point, but will also close the XREF buffer. I never get that right, so I'd like to swap the key bindings, as this makes more sense to me (and is what I want more often in my experience.) Anyone's muscle memories against that? -T.

3 7

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

10 Aug '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1419 slime/ChangeLog:1.1428 --- slime/ChangeLog:1.1419 Fri Aug 8 18:46:54 2008 +++ slime/ChangeLog Sat Aug 9 15:57:37 2008 @@ -1,3 +1,59 @@ +2008-08-09 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-quit-lisp): Optionally send kill signal. + (slime-quit-connection-at-point): Disconnect after some timeout. + +2008-08-09 Helmut Eller <heller(a)common-lisp.net> + + Fixes for heap dumping. + + * swank.lisp (*log-output*): Don't initialize at load-time, + otherwise the stream would end up in a heap image. + +2008-08-09 Helmut Eller <heller(a)common-lisp.net> + + * swank-lispworks.lisp (defimplementation): Record location. + +2008-08-09 Helmut Eller <heller(a)common-lisp.net> + + * swank.lisp (*maximum-pipelined-output-chunks*): New variable + +2008-08-09 Helmut Eller <heller(a)common-lisp.net> + + Display the "Use default debugger" restart more prominently + for testing. + + * swank.lisp (swank-debugger-hook): Bind a user visible restart + to invoke the native debugger. + (*global-debugger*): Make this nil by default. + (sldb-loop): Minor cleanups. + (sldb-break-with-default-debugger): Invoke the native debugger + on top of the slime debugger. + + * slime.el (slime-simple-completions): Bind slime-current-thread + to t so that completion is peformed in a fresh thread. + (sldb-setup): Always pop to the debugger buffer. + (sldb-activate): Optionally select the window. + + * swank-sbcl.lisp (sb-thread::get-foreground): Override this + as the default implementation is unusable for Slime. + + * swank-lispworks.lisp (environment-display-notifier): Just + return t. + +2008-08-09 Helmut Eller <heller(a)common-lisp.net> + + * swank-lispworks.lisp (disassemble-frame): Implemented. + +2008-08-09 Tobias C. Rittweiler <tcr(a)freebits.de> + + M-x slime doesn't destroy the window layout anymore when you + switch windows/frames while the connection is being set up. + + * slime.el (slime-hide-inferior-lisp-buffer): Search for the + inferior-lisp buffer's window in all frames. + (slime-repl-update-banner): Do not pop to the REPL buffer. + 2008-08-08 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el: Fixing `q' in Xref buffers.

1 0

[slime-devel] Proof-of-concept Name-conflict resolution
by Michael Weber 09 Aug '08

09 Aug '08

Hi, attached is a patch for name conflict resolution within SLIME (Zach Beane wrote about the issue quite some time ago: <http://xach.livejournal.com/96625.html >). The patch is not meant for immediate inclusion into SLIME, more as a request for feedback. There are some rough edges in there: * works only with SBCL at the moment. In case of a name conflict, SBCL signals a condition which gives access to the set of conflicting symbols, and also provides a RESOLVE-CONFLICT restart which lets me choose programmatically which symbol to favor out of the conflicting ones. Other Lisps provide different restarts to resolve conflicts, and after superficial looks they appear to be less amenable to programmatic use. * works correctly only with *recent* SBCL (>= 1.0.19.15) * In case of many conflicts (e.g., due to USEing a package), on top of the RESOLVE-CONFLICT restart one can build some automation: instead of ending up a zillion times in the debugger, I can choose to favor a package, and for the current request conflicts are resolved in favor of symbols from that package. If no symbol of the chosen package is in conflict set, I'll end up in the debugger again. I found this behavior quite pleasant to work with in everyday situations. * this is currently realized as a contrib, however, some hooks are needed. I think they are reasonable overall. I provided them as separate patch (0001). * eval-in-emacs is used to trigger the UI (minibuffer & history list--- works for me), which might not be ideal. Cheers, Michael

2 1

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

09 Aug '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1406 slime/ChangeLog:1.1419 --- slime/ChangeLog:1.1406 Thu Aug 7 13:07:22 2008 +++ slime/ChangeLog Fri Aug 8 18:46:54 2008 @@ -1,3 +1,91 @@ +2008-08-08 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el: Fixing `q' in Xref buffers. + + (slime-popup-buffer-snapshot-unchanged-p): New. + (slime-popup-buffer-restore-snapshot): New. + (slime-xref-quit): Can't use slime-popup-buffer directly. Instead + implement its own quit behaviour using the above functions. + +2008-08-08 Helmut Eller <heller(a)common-lisp.net> + + Use wait-for-event instead of catch/throw where needed. + + * swank.lisp (read-user-input-from-emacs, y-or-n-p-in-emacs) + (eval-in-emacs): Use wait-for-event. + (make-tag): Replaces intern-catch-tag. + (take-input): Deleted. + (dispatch-event): Remove some redundancy. + +2008-08-08 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el: Make xref buffers use `slime-with-popup-buffer', + nee `slime-with-temp-buffer'. + + (slime-with-xref-buffer): Rewritten using a popup buffer. + (slime-init-xref-buffer): Removed. + (slime-display-xref-buffer): Removed. + +2008-08-08 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el: Rename slime's temp-buffer to popup-buffer. + +2008-08-08 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-compiler-notes-mode, slime-connection-ist-mode): + Add slime-temp-buffer-mode-map to docstring. + +2008-08-08 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-connections-buffer-name): New variable. + (slime-list-connections): Use it. + (def-slime-selector ?c): Ditto + +2008-08-08 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el: Make the threads browser use `slime-with-temp-buffer'. + + (slime-temp-buffer-quit-function): New buffer-local + variable. Defaults to `slime-temp-buffer-quit'. + (slime-temp-buffer-mode): `q' invokes above variable now. + + (slime-threads-buffer-name): New variable. + (slime-list-threads): Use slime-with-temp-buffer. + (slime-update-threads-buffer): New. Lifted from + slime-list-threads. + (slime-thread-quit): Renamed to slime-quit-threads-buffer. + +2008-08-08 Helmut Eller <heller(a)common-lisp.net> + + Unify event dispatching for single and multi-threaded cases. + + * swank.lisp (send-to-control-thread,read-from-control-thread) + (send-to-socket-io,read-from-socket-io): Deleted. + (send-event, read-event, send-to-emacs) + (signal-interrupt, use-threads-p): New functions. + And more random changes. + +2008-08-08 Helmut Eller <heller(a)common-lisp.net> + + Spawn the auto-flush thread in the front end. + This removes some copy&paste code in various backends. + + * swank.lisp (auto-flush-loop): New function. + (open-streams): Use it. + * swank-backend.lisp (make-stream-interactive): Deleted. + +2008-08-08 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (test disconnect): Call slime-inferior-process + with explicit connection argument to avoid clashes with + buffer-local connections. + +2008-08-08 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-create-macroexpansion-buffer): Make fontifying + case insensitive as the result from macroexpansion is most likely + printed all upper-case. + 2008-08-07 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-with-temp-buffer): By default, no longer inherit

1 0

[slime-devel] Mercurial
by Helmut Eller 08 Aug '08

08 Aug '08

What do people think of switching from CVS to Mercurial[*] ? Helmut. [*] http://www.selenic.com/mercurial/

20 50

[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