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

[slime-devel] LispWorks OS X create-swank-server
by Brian Downing 21 Jun '04

21 Jun '04

I need this patch to make create-swank-server work on Mac OS X LispWorks Personal (v.4.3.7). It works fine on the same version on Windows without it. Without it I get a network error condition: CL-USER 2 > (swank:create-swank-server) Error: BIND failed: (Can't assign requested address) (49) 1 (abort) Return to level 0. 2 Return to top loop level 0. Type :b for backtrace, :c <option number> to proceed, or :? for other options Obviously this is not the solution, but it demonstrates that there's a problem with the :address keyword argument on Mac OS X, at least on my machine. diff -ur slime-pristine/swank-lispworks.lisp slime/swank-lispworks.lisp --- slime-pristine/swank-lispworks.lisp 2004-06-17 10:59:46.000000000 -0500 +++ slime/swank-lispworks.lisp 2004-06-18 14:51:37.000000000 -0500 @@ -37,8 +37,7 @@ (defimplementation create-socket (host port) (multiple-value-bind (socket where errno) - #-lispworks4.1(comm::create-tcp-socket-for-service port :address host) - #+lispworks4.1(comm::create-tcp-socket-for-service port) + (comm::create-tcp-socket-for-service port) (cond (socket socket) (t (error 'network-error :format-control "~A failed: ~A (~D)" -bcd

2 1

[slime-devel] SBCL I/O streams broken?
by Brian Downing 21 Jun '04

21 Jun '04

I've been having a lot of trouble with I/O to SBCL through slime recently. This is on PPC, using either :sigio or :fd-handler communication style, and dedicated-output-stream either t or nil. It's easy for me to reproduce (Slime as of fifteen minutes ago, SBCL 0.8.11.14): CL-USER> (inspect nil) The object is a SYMBOL. 0. Name: "NIL" 1. Package: #<PACKAGE "COMMON-LISP"> 2. Value: NIL 3. Function: "unbound" 4. Plist: NIL > 0 0 0 00 0 0 90 <C-c C-c, select the second to bottom-most reset> ; Evaluation aborted The second to bottom-most one (usually an abort, but not TOPLEVEL) seems the most reliable to clear it up. What's worse is when (as happens on SBCL/PPC sometimes) you get a recursive debug when the backtrace fails, it drops you into a TTY debugger in the Slime REPL. Since you can't interact with it, and it's difficult to get another SLDB debugger to come up, this is kind of bad. I'm not sure when this started. Also, is there any way to get the slime version anymore? The date no longer appears at the top of a repl, which is kind of annoying since it was easy to identify what era of slime you were working with. -bcd -- *** Brian Downing <bdowning at lavos dot net>

1 0

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 21 Jun '04

21 Jun '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.411 slime/ChangeLog:1.417 --- slime/ChangeLog:1.411 Sat Jun 19 22:49:08 2004 +++ slime/ChangeLog Sun Jun 20 23:27:24 2004 @@ -1,3 +1,57 @@ +2004-06-21 Luke Gorrie <luke(a)bluetail.com> + + * swank-loader.lisp (*lisp-name*): Add version number to + Lispwork's fasl directory. We should do this for ACL and OpenMCL + too, but for some reason my ACL 5.0 gets an error when trying to + create a directory with a version number in its name, and I don't + have OpenMCL to test with. + + * swank-backend.lisp, swank.lisp (add-hook, run-hook): Moved the + hook mechanism and all hooks to swank.lisp (from + swank-backend.lisp). There is no compelling use for the hooks in + backends yet and I want to pass swank.lisp-internal data + structures in the existing hooks. + (notify-backend-of-connection): Call `emacs-connected' with the + user-io stream for its argument. Should fix previous breakage + where the connection structure was passed instead. + (*globally-redirect-io*): New configurable: when true the standard + streams are globally redirected to Emacs. That way even + e.g. SERVE-EVENT handlers will print to Emacs. Currently does not + handle standard input -- that is trickier since the Lisp's native + REPL can be trying to read from that. + + * slime.el (slime-complete-maybe-restore-window-configuration): + Only restore the window configuration if the completions buffer is + currently visible in the window that we popped it up in. + (slime-complete-maybe-save-window-configuration): Don't save the + window configuration if the completions buffer is already visible. + (slime-repl-return): Make sure the newline goes at the end of the + input, not at point. + (slime-complete-restore-window-configuration): Wrap the + `set-window-configuration' call in (run-at-time 0 ..). XEmacs does + not allow us to set the window configuration from inside + pre-command-hook. + +2004-06-20 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * swank-sbcl.lisp (emacs-connected): Set *invoke-debugger-hook* to + our debugger hook. Not optimal, but at least BREAK will then + invoke our debugger. + (*trap-load-time-warnings*): New variable. If it is true, + conditions, most notably redefinition warnings, signalled at load + time are not trapped. + (swank-compile-file, swank-compile-string): Use it. + + * swank.lisp (guess-buffer-package): Don't signal a continuable + error if the package doesn't exists; that's too annoying. + + * slime.el: Fix outline structure. + (slime-maybe-list-compiler-notes): Fix thinko. + (break): New test. Reorganize the test-suite a bit to support + "expected failures". + (slime-eval-feature-conditional, slime-to-feature-keyword): Add a + ?: to the symbol-name if needed. + 2004-06-20 Luke Gorrie <luke(a)bluetail.com> * swank.lisp (changelog-date): Removed unneeded function.

1 0

[slime-devel] *new-connection-hook*
by Marco Baringer 21 Jun '04

21 Jun '04

*new-connection-hook* passes the connection struct to emacs-connected which expects a stream argument. something has to be changed. should emacs-connected be changed to take a connection object or should the elements in *new-connection-hook* be passed the stream? -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

3 5

[slime-devel] swank:*globally-redirect-io*
by Luke Gorrie 21 Jun '04

21 Jun '04

Ahoy, I added a new configurable called swank:*globally-redirect-io*. If you set this to true in your ~/.swank.lisp then we hijack the standard streams globally for the duration of the SLIME connection. That way e.g. serve-event handler output will go to the REPL instead of *inferior-lisp*. Currently it doesn't redirect *standard-input*. That's trickier since we can get the Lisp's native REPL trying to read its input from our SLIME REPL :-). You can also globally install SLDB as the debugger like this: (setq *debugger-hook* #'swank:swank-debugger-hook) But that's old news.. Cheers, Luke (who just found his first use for synonym streams)

1 0

[slime-devel] Error when typing `(in-package' in Lisp mode buffer
by Paolo Amoroso 20 Jun '04

20 Jun '04

As soon as I type the "e" of "(in-package" in a Lisp mode buffer, SLIME stops with the error message included below, and reissues the error until I delete enough characters to make the string no longer recognizable as a package setting form. I use SLIME CVS sources updated a few hours ago with GNU Emacs 20.7.2 and CMUCL 18e under Debian Woody. Paolo ----------------------------------------------------------------- Error in function SWANK::GUESS-BUFFER-PACKAGE: Package nil not found. [Condition of type SIMPLE-ERROR] Restarts: 0: [CONTINUE] Use current package. [COMMON-LISP-USER] 1: [ABORT] Abort handling SLIME request. 2: [ABORT] Return to Top-Level. Backtrace: 0: (SWANK::GUESS-BUFFER-PACKAGE "nil") 1: (SWANK::EVAL-FOR-EMACS (SWANK:ARGLIST-FOR-ECHO-AREA '("in-package")) "nil" 11) 2: ("DEFUN HANDLE-REQUEST") 3: (SWANK::CALL-WITH-REDIRECTED-IO #S(SWANK::CONNECTION :SOCKET-IO #<Stream for descriptor 6> :DEDICATED-OUTPUT #1=#<Stream for descriptor 7> :USER-INPUT #2=#<SWANK-BACKEND::SLIME-INPUT-STREAM {48607ECD}> :USER-OUTPUT #1# :USER-IO #<Two-Way Stream, Input = #2#, Output = #1#> ...) #<Function "DEFUN HANDLE-REQUEST" {4845C931}>) 4: (SWANK::HANDLE-REQUEST #S(SWANK::CONNECTION :SOCKET-IO #<Stream for descriptor 6> :DEDICATED-OUTPUT #1=#<Stream for descriptor 7> :USER-INPUT #2=#<SWANK-BACKEND::SLIME-INPUT-STREAM {48607ECD}> :USER-OUTPUT #1# :USER-IO #<Two-Way Stream, Input = #2#, Output = #1#> ...)) 5: (SWANK::PROCESS-AVAILABLE-INPUT #<Stream for descriptor 6> #<Closure Over Function "DEFUN INSTALL-SIGIO-HANDLER" {48682EB1}>) 6: (SWANK::HANDLER) 7: (SWANK-BACKEND::SIGIO-HANDLER #<#1=unused-arg> #<#1#> #<#1#>) 8: ("Foreign function call land") 9: ("Foreign function call land") 10: ("Foreign function call land") 11: ("Foreign function call land") 12: ("Foreign function call land") 13: (SYSTEM:WAIT-UNTIL-FD-USABLE 0 :INPUT NIL) 14: (COMMON-LISP::DO-INPUT #<Stream for Standard Input>) 15: (COMMON-LISP::INPUT-CHARACTER #<Stream for Standard Input> NIL (COMMON-LISP::*EOF*)) 16: (COMMON-LISP::SYNONYM-IN #<Synonym Stream to SYSTEM:*STDIN*> NIL (COMMON-LISP::*EOF*)) 17: (COMMON-LISP::TWO-WAY-IN #<Two-Way Stream, Input = #<Synonym Stream to SYSTEM:*STDIN*>, Output = #<Synonym Stream to SYSTEM:*STDOUT*>> NIL (COMMON-LISP::*EOF*)) 18: (READ-CHAR #<Two-Way Stream, Input = #<Synonym Stream to SYSTEM:*STDIN*>, Output = #<Synonym Stream to SYSTEM:*STDOUT*>> NIL (COMMON-LISP::*EOF*) #<unused-arg>) 19: (READ-PRESERVING-WHITESPACE #<Two-Way Stream, Input = #<Synonym Stream to SYSTEM:*STDIN*>, Output = #<Synonym Stream to SYSTEM:*STDOUT*>> NIL (:EOF) T) 20: (READ-PRESERVING-WHITESPACE #<Two-Way Stream, Input = #<Synonym Stream to SYSTEM:*STDIN*>, Output = #<Synonym Stream to SYSTEM:*STDOUT*>> NIL (:EOF) NIL) 21: (READ-PRESERVING-WHITESPACE 4 #<Two-Way Stream, Input = #<Synonym Stream to SYSTEM:*STDIN*>, Output = #<Synonym Stream to SYSTEM:*STDOUT*>> NIL (:EOF) ...)[:EXTERNAL] 22: (READ #<Two-Way Stream, Input = #<Synonym Stream to SYSTEM:*STDIN*>, Output = #<Synonym Stream to SYSTEM:*STDOUT*>> NIL (:EOF) NIL) 23: (COMMON-LISP::%TOP-LEVEL) 24: (COMMON-LISP::RESTART-LISP) ----------------------------------------------------------------- -- Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film

1 1

[slime-devel] Compilation policy in and out of Slime
by Brian Downing 20 Jun '04

20 Jun '04

[Slime 2004-06-18, SBCL Darwin/PPC 0.8.11.14+many hacks, an oldish Emacs CVS] Once thing I noticed when working on some SBCL internals tonight is that Slime is compiling things for SBCL with very little debug. This can be seen by compiling: (defun bar (x y) (zot x y)) from the Slime REPL and the *inferior-lisp* REPL. The Slime-compiled one has a very short disassembly, and tail-calls the FDEFINITION. The REPL-compiled one is quite long, and doesn't. This is strange, though, since sb-c::*policy* evaluates to the same in either environment. While this was sort of nice for me (Slime's low debug made my find and fix a nasty stack-destroying bug), it seems bad that Slime-compiled code is defaulting to low debug levels, and seems to not be respecting the *policy*. Is this happening on anyone else's installation, and does anyone have an idea why this is happening? (I've not CCed sbcl-devel on this - I figure enough of the SBCL developers who know anything about Slime are on this list.) -bcd

1 1

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 20 Jun '04

20 Jun '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.409 slime/ChangeLog:1.411 --- slime/ChangeLog:1.409 Fri Jun 18 14:54:34 2004 +++ slime/ChangeLog Sat Jun 19 22:49:08 2004 @@ -1,3 +1,46 @@ +2004-06-20 Luke Gorrie <luke(a)bluetail.com> + + * swank.lisp (changelog-date): Removed unneeded function. + (connection-info): No more version field in result. + + * slime.el: Audited to remove namespace slipups. Tracking a really + horrible clashing-with-some-user-configuration bug and want to + eliminate potential symbol conflicts. + (sldb-get-buffer): Renamed from `get-sldb-buffer'. + (slime-emacs-20-p): Renamed from `emacs-20-p'. + (slime-defun-if-undefined): Renamed from `defun-if-undefined'. + (slime-isearch): Small bugfix that could cause M-. to go to the + wrong place in CMUCL. + (slime-changelog-date, slime-check-protocol-version): Removed + unneeded functions. + + * swank-backend.lisp (add-hook, run-hook): Added an Emacs-like + hook mechanism. The hope is that this will make some sections of + the code more self-describing by showing where they hook in. + (*new-connection-hook*): Hook run when a new connection is + established. Initialized to '(swank-backend:emacs-connected). + (*pre-reply-hook*): Hook run before sending a reply to Emacs. + + * swank.lisp: Added some comments and docstrings. + (package-external-symbols): Removed unused function. + (serve-connection): Call *new-connection-hook*. + (eval-for-emacs): Call *pre-reply-hook*. + (sync-features-to-emacs, sync-indentation-to-emacs): Added to + *pre-reply-hook*. + (cl-package, keyword-package): Now defconstant instead of + defvar. Removed the *'s accordingly. + + * slime.el (slime-abort-connection): Renamed from + `slime-connection-abort'. The new name is easier to find with + completion. + + * swank-sbcl.lisp: Change sb-posix:: to sb-posix: + +2004-06-19 Luke Gorrie <luke(a)bluetail.com> + + * swank.lisp (known-to-emacs-p): Bugfix. Indentation-updates was + broken. + 2004-06-18 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-buffer-package): If DONT-CACHE is true and no

1 0

[slime-devel] M-x slime to go back to the REPL
by Pascal J.Bourguignon 20 Jun '04

20 Jun '04

Both ilisp and run-lisp when invoked a second time switch back to their buffer. slime did not. Now it does too: (defun slime () "Start an inferior^_superior Lisp and connect to its Swank server, or switch to the slime REPL buffer if it's already running." (interactive) (if (get-buffer-process (get-buffer "*inferior-lisp*")) (switch-to-buffer (slime-output-buffer)) (when (or (not (slime-bytecode-stale-p)) (slime-urge-bytecode-recompile)) (cond ((and current-prefix-arg (slime-connected-p) (get-buffer "*inferior-lisp*")) (unless (slime-maybe-rearrange-inferior-lisp) (slime-disconnect))) (t (slime-disconnect))) (slime-maybe-start-lisp) (slime-read-port-and-connect)))) -- __Pascal Bourguignon__ http://www.informatimago.com/ There is no worse tyranny than to force a man to pay for what he does not want merely because you think it would be good for him. -- Robert Heinlein

1 0

[slime-devel] splash patch version 3
by Pascal J.Bourguignon 20 Jun '04

20 Jun '04

Thanks to user feedback, here is the third release of the splash screen for slime. Added: - selection of splash-dark.png or splash-light.png depending on the dark/light status of the frame. - search the splash-*.png files first in ~/.slime/, then in load-paths. That should give each user an opportunity to have his own splash screen. splash-3.patch, to be applied after the previous patch. -- __Pascal Bourguignon__ http://www.informatimago.com/ There is no worse tyranny than to force a man to pay for what he does not want merely because you think it would be good for him. -- Robert Heinlein

1 0

[slime-devel] splash patch
by Pascal J.Bourguignon 20 Jun '04

20 Jun '04

Since I cannot go pass the Initial Handshake, here is some initial eye sugar: a splash screen for slime. The patch includes in addition for clisp: - specifying the package to unlock when redefining BREAK (COMMON-LISP), - *slime-load-verbose* and swank-loader:*swank-load-verbose* variables to avoid all these Loading/Loaded messages. (The diffs are from the FAIRLY_STABLE release. Just ask if you want them from HEAD). -- __Pascal Bourguignon__ http://www.informatimago.com/ There is no worse tyranny than to force a man to pay for what he does not want merely because you think it would be good for him. -- Robert Heinlein

1 1

[slime-devel] slime/clisp hang: tcpdump
by Pascal J.Bourguignon 20 Jun '04

20 Jun '04

Here is the output of tcpdump -s 0 -i lo -w /tmp/capture.pcap on my slime/clisp hanging. -- __Pascal Bourguignon__ http://www.informatimago.com/ There is no worse tyranny than to force a man to pay for what he does not want merely because you think it would be good for him. -- Robert Heinlein

1 2

[slime-devel] Towards 1.0?
by Luke Gorrie 20 Jun '04

20 Jun '04

Howdidlydoo, I'm feeling impulsive lately. How about shooting for a 1.0 release? I know some people are already in favour (hi Brian :-), so I'm particularly probing for the opinion of the other side (hi Helmut :-) >From my end there are a lot of good omens for an August 27 release: It will be the one-year anniversary of the first public mention [1] of SLIME. (Time really flies!) It will be my birthday. (*) I'll be starting a new job, and be really busy for a while. How do the tea leaves look for you guys? Cheers, Luke [1]: The fateful posting of a tweak to Eric Marsden's SLIM on a list that Helmut reads: http://thread.gmane.org/gmane.lisp.cmucl.devel/3850 (*): How sad is it that I apparently spent my 25th birthday hacking Emacs? :-)

9 20

[slime-devel] Slime hangs emacs in Initial handshake / complements
by Pascal J.Bourguignon 19 Jun '04

19 Jun '04

I forgot to write that C-g in emacs does not produce any effect, I have to kill it, and the processes are in these states: 10985 pts/1 R 12:09 \_ emacs 10986 ? S 0:00 \_ /usr/local/libexec/emacs/21.3/i686-pc-linux-gnu/emacsserve 11004 pts/4 S 0:11 \_ /local/languages/clisp//lib/clisp/full/lisp.run -B /local/ ........................................................................ Hello, I tried both with HEAD and FAIRLY_STABLE, when I run M-x slime RET, it loads clisp and the swap files (that it compiles along) and then: WARNING: These Swank interfaces are unimplemented: (ADD-FD-HANDLER ADD-SIGIO-HANDLER ALL-THREADS DISASSEMBLE-FRAME GETPID INTERRUPT-THREAD RECEIVE REMOVE-FD-HANDLERS REMOVE-SIGIO-HANDLERS SEND SPAWN WHO-MACROEXPANDS WHO-SPECIALIZES) ;; Loaded file /usr/local/share/emacs/site-lisp/slime/swank-loader.lisp T [2]> ;; Swank started at port: 33514 ------------------------------------------------------------------------ -1:** *inferior-lisp* Sat Jun 19 20:59 0.55 (Inferior Lisp:run Inf-Slime[polling ------------------------------------------------------------------------ Initial handshake... (show (version)) ;; --> "GNU Emacs 21.3.1 (i686-pc-linux-gnu) of 2003-10-27 on thalassa" (show inferior-lisp-program) ;; --> "/usr/local/bin/clisp -ansi -q -K full -m 32M -I -E ISO-8859-1" GNU CLISP 2.33 (2004-03-17) (built 3289566600) (memory 3289567213) Software: GNU C 3.3 20030226 (prerelease) (SuSE Linux) ANSI C program Features: (CLOS LOOP COMPILER CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX) Installation directory: /local/languages/clisp/lib/clisp/ User language: ENGLISH Machine: I686 (I686) thalassa.informatimago.com [62.93.174.79] -- __Pascal Bourguignon__ http://www.informatimago.com/ There is no worse tyranny than to force a man to pay for what he does not want merely because you think it would be good for him. -- Robert Heinlein

4 5

[slime-devel] Slime hangs emacs in Initial handshake.
by Pascal J.Bourguignon 19 Jun '04

19 Jun '04

Hello, I tried both with HEAD and FAIRLY_STABLE, when I run M-x slime RET, it loads clisp and the swap files (that it compiles along) and then: WARNING: These Swank interfaces are unimplemented: (ADD-FD-HANDLER ADD-SIGIO-HANDLER ALL-THREADS DISASSEMBLE-FRAME GETPID INTERRUPT-THREAD RECEIVE REMOVE-FD-HANDLERS REMOVE-SIGIO-HANDLERS SEND SPAWN WHO-MACROEXPANDS WHO-SPECIALIZES) ;; Loaded file /usr/local/share/emacs/site-lisp/slime/swank-loader.lisp T [2]> ;; Swank started at port: 33514 ------------------------------------------------------------------------ -1:** *inferior-lisp* Sat Jun 19 20:59 0.55 (Inferior Lisp:run Inf-Slime[polling ------------------------------------------------------------------------ Initial handshake... (show (version)) ;; --> "GNU Emacs 21.3.1 (i686-pc-linux-gnu) of 2003-10-27 on thalassa" (show inferior-lisp-program) ;; --> "/usr/local/bin/clisp -ansi -q -K full -m 32M -I -E ISO-8859-1" GNU CLISP 2.33 (2004-03-17) (built 3289566600) (memory 3289567213) Software: GNU C 3.3 20030226 (prerelease) (SuSE Linux) ANSI C program Features: (CLOS LOOP COMPILER CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX) Installation directory: /local/languages/clisp/lib/clisp/ User language: ENGLISH Machine: I686 (I686) thalassa.informatimago.com [62.93.174.79] -- __Pascal Bourguignon__ http://www.informatimago.com/ There is no worse tyranny than to force a man to pay for what he does not want merely because you think it would be good for him. -- Robert Heinlein

1 0

[slime-devel] CVS down?
by Pascal J.Bourguignon 19 Jun '04

19 Jun '04

% export CVSROOT=:pserver:anonymous@common-lisp.net:/project/slime/cvsroot $ cvs login Logging in to :pserver:anonymous@common-lisp.net:2401/project/slime/cvsroot CVS password: anonymous % cvs checkout slime cvs [checkout aborted]: connect to common-lisp.net(69.55.225.117):2401 failed: Connection refused $ ping common-lisp.net PING common-lisp.net (69.55.225.117) 56(84) bytes of data. 64 bytes from common-lisp.net (69.55.225.117): icmp_seq=1 ttl=46 time=243 ms 64 bytes from common-lisp.net (69.55.225.117): icmp_seq=2 ttl=47 time=241 ms 64 bytes from common-lisp.net (69.55.225.117): icmp_seq=3 ttl=46 time=241 ms 64 bytes from common-lisp.net (69.55.225.117): icmp_seq=4 ttl=46 time=242 ms Is this normal? Did I do something wrong? -- __Pascal Bourguignon__ http://www.informatimago.com/ There is no worse tyranny than to force a man to pay for what he does not want merely because you think it would be good for him. -- Robert Heinlein

1 1

[slime-devel] slime-with-output-to-temp-buffer small fix
by Rui Patrocínio 19 Jun '04

19 Jun '04

Hello, When invoking something in a temp buffer, the old window configuration is erased by the current one. I don't know if this is a bug but it's a little annoying, so here is a small fix. Rui Patrocínio

1 0

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 19 Jun '04

19 Jun '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.401 slime/ChangeLog:1.409 --- slime/ChangeLog:1.401 Thu Jun 17 10:42:39 2004 +++ slime/ChangeLog Fri Jun 18 14:54:34 2004 @@ -1,3 +1,38 @@ +2004-06-18 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-buffer-package): If DONT-CACHE is true and no + package name can be found, then default to "COMMON-LISP-USER." + Previously we just kept using the cached version, but that could + lead to error-after-error if it was incorrect. + + * swank.lisp (throw-to-toplevel): If our top-level catcher isn't + on the stack (i.e. we're using the debugger from outside an RPC) + then ABORT instead. That makes 'q' DWIM in SLDB. + +2004-06-18 Matthew Danish <mdanish(a)andrew.cmu.edu> + + * swank-allegro.lisp (frame-source-location-for-emacs): + Implemented. + +2004-06-18 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-repl-return): If the user presses return on old + REPL input then take it and insert it as the current input. + Signal an error if the point is not on any input. + (slime-preserve-zmacs-region): Function to ensure that the current + command doesn't deactivate zmacs-region (XEmacs only). + (slime-repl-bol, slime-repl-eol): Use it. + (slime-kill-all-buffers): Changed buffer-name regexps for XEmacs + compatibility. The ",quit" shortcut now works in XEmacs. + (slime-display-message): Fixed call to `slime-typeout-message' + to handle formatting characters. Avoids errors on certain messages. + (slime-list-compiler-notes): Save the window configuration + earlier. This fixes an error under XEmacs when dismissing the + notes buffer. + (slime-recenter-window): Avoid moving the point. This keeps the + point in the right place when showing debugger-frame locations in + Emacs 21. + 2004-06-17 Luke Gorrie <luke(a)bluetail.com> * swank-loader.lisp (binary-pathname): Place fasl files under

1 0

[slime-devel] Would like to add 'changed definitions' functionality
by Glenn Ehrlich 18 Jun '04

18 Jun '04

Hi, I'd like to add some sort of 'changed definitions' functionality to slime, i.e., be able to to evaluate or compile changed defs in the buffer or all buffers. I'm thinking of modeling this after the changed definitions of Genera (from my new lisp machine :) or LispWorks. I've looked at the similar functionality in ilisp (but you have to manually mark functions) and Franz's eli (which looks like it might be a good starting point). Any particular hints or comments folks would like to make before I start? Any internal functions that might be helpful? -- Glenn Ehrlich http://cooking-with-lisp.blogspot.com

3 4

Re: [slime-devel] SLIME User Survey
by Bill_Clementson＠peoplesoft.com 18 Jun '04

18 Jun '04

> Questions: > > Which Lisp versions do you use SLIME with? Allegro 6.2 and 7.0beta, LispWorks 4.3, CLISP 2.33, and ABCL (cvs) - all on Win2000 > Which Emacs versions? GNU Emacs 21.3.50 > How well does SLIME work for you? Great! I used ILISP and ELI in the past, but SLIME seems to have the best mix of features, stability and portability. I only use SLIME today. > What bugs (reproducible or otherwise) or missing features annoy you? bug: the "v"iew source option in sldb doesn't work for any implementation I'm using feature: it would be *really* nice to have edebug-like debugging in SLIME > Is there some packaging system (e.g. Debian) that you would like to > see SLIME 1.0 bundled with? If so, do you know how to coordinate this? Windows installer - just joking ;-) Debian seems the obvious choice (although I don't use Linux). Kevin Rosenberg has done a fantastic job looking after a lot of the CL packages on Debian (have a look at http://b9.com/debian.html to see a list of the ones he maintains). You might try twisting his arm a little to get him to look after SLIME too :-) > If you said anything negative above then please say something nice > here to make us feel good: SLIME just seems to go from strength to strength - great job you guys! - Bill

1 0

Re: [slime-devel] Re: Towards 1.0?
by Bill_Clementson＠peoplesoft.com 18 Jun '04

18 Jun '04

Luke Gorrie <luke(a)bluetail.com> writes: > Helmut Eller <e9626484(a)stud3.tuwien.ac.at> writes: > > Are there any features we can remove? I was going to suggest removing > > the REPL (because the code is messy and a REPL is not the Emacs way to > > interact with anything), but I guess people wouldn't like that :-) > > Amazingly I find myself using the REPL all the time, even though I > never use IELM for Emacs Lisp. I'm not sure why. I also use the REPL all the time and wouldn't like to see it removed. In fact, my normal modus operandi is to jump between source window and REPL, sometimes evaluating sexp's in the source window, sometimes evaluating them in the REPL. Generally, the one-off testing stuff is in the REPL; however, there are often times when I want to step through chunks of code from a source buffer in the REPL and "tweak" the code before it is executed. for that, I use the following function: (defun slime-present () (interactive) (setq *presentation-buffer* (current-buffer)) (global-set-key [f9] (lambda () (interactive) (set-buffer *presentation-buffer*) (forward-sexp) (let ((end (point)) (beg (save-excursion (backward-list 1) (point)))) (copy-region-as-kill-nomark beg end) (set-buffer (slime-output-buffer)) (unless (eq (current-buffer) (window-buffer)) (pop-to-buffer (current-buffer) t)) (goto-char (point-max)) (yank) (slime-reindent-defun) (delete-other-windows))))) This is also useful when I want to give a "slide show" type of presentation of some lisp code or when I want a "clean" REPL session (e.g. -- if I want to post it later to my weblog). So, to reiterate, I LIKE THE REPL. :-) > > Any outstanding keybinding wars? A while ago we talked about grouping > > documentation commands under C-c C-d; I like that idea. > > Agree. We should also move hyperspec-lookup so that `C-c C-h' does the > default action of listing all bindings starting with C-c, and move the > funky-indentation C-M-q command because it's different to the standard > indentation command on that binding (does a whole defun, not sexp at > point). While on the subject of the "grouping" commands, one personal little nitpick that I have is that I don't like the "C-c C-w m" type "grouped" commands. I find that it is easier (and less error prone) for me to type "C-c C-w C-m" instead of "C-c C-w m" because I don't have to lift my finger off the control key to press the m. This was something that we had a number of discussions about among the ILISP developers a while back and the general consensus was in support of the 3-control key sequence. What do others think about this? - Bill

2 1

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 18 Jun '04

18 Jun '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.397 slime/ChangeLog:1.401 --- slime/ChangeLog:1.397 Wed Jun 16 15:05:27 2004 +++ slime/ChangeLog Thu Jun 17 10:42:39 2004 @@ -1,3 +1,18 @@ +2004-06-17 Luke Gorrie <luke(a)bluetail.com> + + * swank-loader.lisp (binary-pathname): Place fasl files under + ~/.slime/fasl/ instead of the SLIME installation directory. The + installation directory can now be read-only. + (binary-pathname, user-init-file): Removed Win32 + conditionalization. The init file is now called ~/.swank.lisp + instead of ~/_swank.lsp. + + * swank-lispworks.lisp (with-fairly-standard-io-syntax): New + macro. Like with-standard-io-syntax, but keeps the existing values + of *package* and *readtable*. + (dspec-stream-position): Use it. + (quit-lisp): Implemented. + 2004-06-16 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * slime.el (slime-set-default-directory): Don't call

1 0

[slime-devel] Broken readtables
by Alain.Picard＠memetrics.com 17 Jun '04

17 Jun '04

I have a file which defines a readtable so I can type things like #v(1 2). (Don't ask. :-) When I hit M-. to find any definition in this file, emacs croaks and asks if I want to enter recursive edit. Saying yes yields a SLDB buffer like this: Subcharacter #\v not defined for dispatch char #\#. [Condition of type CONDITIONS:SIMPLE-READER-ERROR] Restarts: 0: [ABORT] Abort handling SLIME request. 1: [ABORT] Quit process. Now, I grovelled a bit in the sources and found: (defvar *readtable-alist* '() "An alist mapping package names to readtables.") I tried to use this thusly: Try to add what I think is reasonable to this alist CL-USER> (push (cons "GRAPHICS" *readtable*) swank::*readtable-alist*) (("GRAPHICS" . #<READTABLE 202E1B84>)) Verify that it finds the right package CL-USER> (swank::guess-buffer-readtable "graphics") #<READTABLE 202E1B84> Make sure the correct table is in place: CL-USER> (get-dispatch-macro-character #\# #\v (swank::guess-buffer-readtable "graphics")) #<function GRAPHICS::VECTOR-READER 237CF9D2> (looks good). However, the next M-. failed in exactly the same way. Tracing GUESS-BUFFER-READTABLE, I found it was in fact calling it with argument ":graphics", which I thought sub-optimal, but, no matter: CL-USER> (push (cons ":graphics" *readtable*) swank::*readtable-alist*) ((":graphics" . #<READTABLE 202E1B84>) ("GRAPHICS" . #<READTABLE 202E1B84>)) Now, surely it will work, right? Nope. Any clues? Cheers, --ap

5 9

Re: [slime-devel] Re: Towards 1.0?
by Bill_Clementson＠peoplesoft.com 17 Jun '04

17 Jun '04

Luke Gorrie <luke(a)bluetail.com> writes: > Helmut Eller <e9626484(a)stud3.tuwien.ac.at> writes: > > > Where should install we SLIME by default? A writable directory would > > be the easiest for us; not sure if distributors like that. > > I hacked swank-loader.lisp to put the fasl files in ~/.slime/fasl/ (on > Win32 it's _slime instead). This way we can install in a read-only > directory. Sound okay? I use Win32 and have plenty of directories in my home directory that start with "dot". There's no reason to make a special exception for Win32 - I would prefer to have the directory name be the same for both Win32 and non-Win32 installs. Another advantage is that, in Emacs, you can elect to not have your dot directories displayed in dired buffers. This is my preference for the fasl directories as I don't normally want to drill down into them. - Bill

4 4

Re: [slime-devel] Re: Towards 1.0?
by Bill_Clementson＠peoplesoft.com 17 Jun '04

17 Jun '04

Luke Gorrie <luke(a)bluetail.com> writes: > Bill_Clementson(a)peoplesoft.com writes: > > > I use Win32 and have plenty of directories in my home directory that start > > with "dot". There's no reason to make a special exception for Win32 > > Sounds good to me. But it begs the question: why are we already making > an exception of ~/_swank.lsp vs. ~/.swank.lisp for the init file? > Anyone? Probably because of: 1. Historical Windows/Emacs reasons (older versions of NTEmacs required that the .emacs file be named "_emacs"; however, current versions allow you to use either "_emacs" or ".emacs" as the default initialization file name.) 2, Because some brain-dead Win32 programs won't let you create a file that starts with dot (Windows Explorer is a prime example). However, Emacs on Win32 will let you do this and if you're using slime, you're using Emacs, right? :-) In fact, now even notepad on Win32 will allow you to create files with a dot at the beginning of their name. > Bill, is there some code we can snarf from your blog to make > installation on Win32 easier? We should at least fold your > instructions into the manual. Sure, feel free to grab anything that is useful. I think that most of my slime-related weblog postings are linked to from the "SLIME HOW-TO" page on CLiki (http://www.cliki.net/SLIME-HOWTO) - Bill

1 0