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

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 23 Jan '04

23 Jan '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.232 slime/ChangeLog:1.233 --- slime/ChangeLog:1.232 Thu Jan 22 00:24:35 2004 +++ slime/ChangeLog Thu Jan 22 19:20:58 2004 @@ -1,3 +1,14 @@ +2004-01-23 Michael Weber <michaelw(a)foldr.org> + + * slime.el (slime-repl-set-package): New command to set the + package in the REPL buffer. + + * swank.lisp (set-package): Return the shortest nickname. + +2004-01-23 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (sldb-disassemble): Was lost somewhere. + 2004-01-22 Wolfgang Jenkner <wjenkner(a)inode.at> * swank-clisp.lisp: Replace defmethod by defimplementation where @@ -20,8 +31,8 @@ * swank-backend.lisp (return-from-frame, restart-frame): Are now interface functions. - * slime/swank.asd: Remove dependency on :sb-bsd-sockets. Is - already done in swank-sbcl. + * swank.asd: Remove dependency on :sb-bsd-sockets. Is already + done in swank-sbcl. * swank-loader.lisp: Don't reference the swank package at read-time.

1 0

[slime-devel] buglet hyperspec.el: hyperspec-lookup copies text properties at point
by Michael Weber 23 Jan '04

23 Jan '04

Hi, HYPERSPEC-LOOKUP from slime's hyperspec.el copies the emacs text properties when getting the symbol to lookup. When called at a new slime-repl prompt, the prompt is taken as symbol to lookup (since there is nothing else). But the slime-repl prompt has property read-only and thus it cannot be edited at the HYPERSPEC-LOOKUP prompt in the minibuffer, to enter the right symbol for lookup. * to reproduce: M-x slime M-x hyperspec-lookup ; try to edit the "CL-USER>", emacs will beep and whine that it is ; read-only. * software: + Latest SLIME + GNU/Emacs 21.3.50.1 * fix: Drop text-properties when getting symbol at point. Ideally, thingatpt would provide such functionality, but it does not, currently. Patch for hyperspec.el attached. Cheers, Michael

2 2

[slime-devel] swank-loader
by Marco Baringer 22 Jan '04

22 Jan '04

when using asdf to load swank the file swank-loader.lisp is compilied, however this file contains a symbol in the swank package, which is fine when the file is loaded but is an error when the file is compiled before the rest of swank has been loaded, which is what asdf tries to do when loading the swank system. anyway, attached is a new swank.asd which contains all the dependencies in swank-loader and can be loaded from a non-emacs staret lisp image. since i'm going to assume swank.asd will be used by programs and not by users (via emacs) this asdf doesn't load the user's init file. -- Marco Ring the bells that still can ring. Forget the perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

6 16

[slime-devel] SLIME buglet: The value NIL is not of type PACKAGE.
by Michael Weber 22 Jan '04

22 Jan '04

This is CVS HEAD from 5mins ago: To reproduce: M-x slime ; start SLIME C-x C-f foo.lisp ; get a buffer in lisp-mode C-c : ; Slime Eval: <Tab> ; slime-completie-symbol The value NIL is not of type PACKAGE. [Condition of type TYPE-ERROR] Restarts: 0: [ABORT] Return to SLIME toplevel. 1: [ABORT] Reduce debugger level (leaving debugger, returning to toplevel). 2: [TOPLEVEL] Restart at toplevel READ/EVAL/PRINT loop. Backtrace: 0: (SWANK:COMPLETIONS "Eval: " NIL) 1: (SB-INT:EVAL-IN-LEXENV 2 (SWANK:COMPLETIONS "Eval: " NIL) #S(SB-KERNEL:LEXENV :FUNS NIL :VARS NIL :BLOCKS NIL :TAGS NIL :TYPE-RESTRICTIONS NIL :LAMBDA NIL :CLEANUP NIL :POLICY ((SPEED . 1) (SPACE . 1) (SAFETY . 1) (INHIBIT-WARNINGS . 1) (DEBUG . 1) (COMPILATION-SPEED . 1))))[:EXTERNAL] 2: (SWANK:EVAL-STRING "(swank:completions \"Eval: \" nil)" NIL 19) 3: ("hairy arg processor for SWANK::READ-FROM-EMACS" #<FILE-STREAM for "a constant string" {9915711}>)

3 4

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 22 Jan '04

22 Jan '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.230 slime/ChangeLog:1.232 --- slime/ChangeLog:1.230 Tue Jan 20 16:53:15 2004 +++ slime/ChangeLog Thu Jan 22 00:24:35 2004 @@ -1,3 +1,80 @@ +2004-01-22 Wolfgang Jenkner <wjenkner(a)inode.at> + + * swank-clisp.lisp: Replace defmethod by defimplementation where + appropriate. + (return-from-frame, restart-frame): Implement them. + +2004-01-22 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * test.sh: Copy the ChangeLog file too. + + * swank-cmucl.lisp: Replace some defmethods with + defimplementation. + + * swank-allegro.lisp (return-from-frame, restart-name): Implement + interface (partly). + + * swank-openmcl.lisp (restart-frame, return-from-frame): Remove + sldb-prefix. + + * swank-backend.lisp (return-from-frame, restart-frame): + Are now interface functions. + + * slime/swank.asd: Remove dependency on :sb-bsd-sockets. Is + already done in swank-sbcl. + + * swank-loader.lisp: Don't reference the swank package at + read-time. + + * swank.lisp (completions): Never bind *package* to nil. That's a + type error in SBCL. + (swank-debugger-hook): Flush the output streams and be careful + when accessing *buffer-package*. + (create-swank-server): Return the port of the serve socket. + + * swank-lispworks.lisp (interesting-frame-p): Don't print catch + frames. + (make-sigint-handler): New function. + (emacs-connected): Use it. + + * slime.el (slime-lisp-implementation-type): New per connection + variable. + (slime-handle-oob): Handle debug-condition event. Can be signaled + CMUCL when cannot produce a backtrace. + (slime-debugging-state): Don't pop up the debugger buffer an + activate events. Annoying. + (sldb-break-with-default-debugger): Switch to the output buffer + before returning to the tty-debugger. + (sldb-return-from-frame, sldb-restart-frame): Use slime-rex. + (slime-list-connections, slime-short-state-name): New functions. + +2004-01-20 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-complete-symbol): Insert the completed-prefix + before deleting the original text to avoid troubles with left + inserting markers. + (slime-symbol-start-pos): Skip backward across symbol + constituents. + (slime-evaluating-state): [:read-sring] Save the window + configuration. + (slime-read-string-state): Don't handle activate events + (troublesome if, e.g, complete-symbol is used from another + buffer). Restore the window configuration. + (slime-repl-read-string): Goto the end of buffer. + (slime-debugging-state): [:activate] Display the debugger buffer + if not visible. + (slime-to-lisp-filename, slime-from-lisp-filename) + (slime-translate-to-lisp-filename-function) + (slime-translate-from-lisp-filename-function, slime-compile-file) + (slime-goto-location-buffer, slime-ed, slime-load-file): Support + for remote filename translation (untested). + + * swank.lisp (create-swank-server): Take announce-fn as optional + argument. + + * swank-allegro.lisp: Replace defmethod with defimplementation. + (eval-in-frame): Implemented. + 2004-01-20 Lasse Rasinen <lrasinen(a)iki.fi> * slime.el (slime-prin1-to-string): Replacement for @@ -1699,7 +1776,7 @@ tty. Output streams are now line buffered. We no longer compute the backtrace-length. - * /project/slime/cvsroot/slime/slime.el: + * slime.el: (slime-repl-read-mode, slime-repl-read-string, slime-repl-return, slime-repl-send-string, slime-read-string-state, slime-activate-state): Reorganize input redirection. We no longer

1 0

[slime-devel] startup problem
by raymond 22 Jan '04

22 Jan '04

i get the following error when starting SLIME, on Debian / sbcl fresh from CVS, SLIME farily recent. please help. -------------------------------------------------------- CL-USER> debugger invoked on a SB-INT:SIMPLE-PROGRAM-ERROR in thread 2825: invalid number of arguments: 2 You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT ] Reduce debugger level (leaving debugger, returning to toplevel). 1: [TOPLEVEL] Restart at toplevel READ/EVAL/PRINT loop. ("XEP for EVAL-STRING" 2 "(swank:getpid)" NIL 1)[:EXTERNAL] source: (DEFSLIMEFUN EVAL-STRING (STRING BUFFER-PACKAGE ID) (LET ((*PROCESSING-RPC* T) (*DEBUGGER-HOOK* #'SWANK-DEBUGGER-HOOK)) (LET (OK RESULT) (UNWIND-PROTECT (LET # # # # #) (SYNC-STATE-TO-EMACS) (FORCE-OUTPUT *SLIME-IO*) (SEND-TO-EMACS `#)))) (WHEN *DEBUGGER-HOOK-PASSBACK* (SETQ *DEBUGGER-HOOK* *DEBUGGER-HOOK-PASSBACK*) (SETQ *DEBUGGER-HOOK-PASSBACK* NIL))) 0]

2 1

[slime-devel] swank-create-server (round II)
by Marco Baringer 22 Jan '04

22 Jan '04

imho swank-create-server is much more convient if it returns the port number it has opened. 4 line patch follows. p.s. - am i the only one actually using create-swank-server? -- Marco Ring the bells that still can ring. Forget the perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

2 3

[slime-devel] Lispworks multiprocessing (?) problem
by Alain.Picard＠memetrics.com 21 Jan '04

21 Jan '04

Fellow slimers, I have a (Lispworks) console image in which I load some files, then run a function which starts multiprocessing, e.g. XOS> (load-server) ;;; hundreds of lines of stuff loading here... XOS> (main-thread) .............DONE! XOS> I've set this console to be my LISP-PROGRAM, and M-x slime starts it all up fine. After step 1, I can play around source files, compiling forms with C-c C-c. After step 2, most interactions land me in this state: ;;; Compiling file /tmp/filerbPYBy.lisp ... ;;; Safety = 3, Speed = 1, Space = 1, Float = 1, Interruptible = 0 ;;; Compilation speed = 1, Debug = 2, Fixnum safety = 3 ;;; Source level debugging is on ;;; Source file recording is on ;;; Cross referencing is on ; Loading fasl file /tmp/filerbPYBy.ufsl 1 Error: The variable SWANK::*BUFFER-PACKAGE* is unbound. 1 Try evaluating SWANK::*BUFFER-PACKAGE* again. 2 Specify a value to use this time instead of evaluating SWANK::*BUFFER-PACKAGE*. 3 Specify a value to set SWANK::*BUFFER-PACKAGE* to. 4 (continue) Retry assertion. 5 (abort) Return to level 0. 6 Return to top loop level 0. Type :b for backtrace, :c <option number> to proceed, or :? for other options CL-USER 3 : 1 > :b Call to SWANK::SWANK-DEBUGGER-HOOK Call to INVOKE-DEBUGGER Call to SWANK::FORCE-USER-OUTPUT Call to SWANK:EVAL-STRING Call to FUNCALL Call to SWANK::READ-FROM-EMACS Call to SWANK::READ-USER-INPUT-FROM-EMACS Call to (SUBFUNCTION 1 SWANK::CREATE-CONNECTION) Call to (METHOD STREAM:STREAM-READ-CHAR (SWANK::SLIME-INPUT-STREAM)) Call to IO::READ-OBJECT Call to IO::RECURSIVE-READ Call to READ-PRESERVING-WHITESPACE Call to EDITOR:RUBBER-READ-A-COMMAND Call to (SUBFUNCTION MP::PROCESS-SG-FUNCTION MP::INITIALIZE-PROCESS-STACK) CL-USER 4 : 1 > If I try to continue with the 2nd restart, to specify a value for SWANK::*BUFFER-PACKAGE*, no joy either: CL-USER 6 : 1 > :c 2 (find-package :xos) Enter a form to be evaluated: Error: NIL is not of type SWANK::CONNECTION when accessing slot SWANK::SOCKET-IO. 1 (continue) Retry assertion. 2 (abort) Return to level 0. 3 Return to top loop level 0. Type :b for backtrace, :c <option number> to proceed, or :? for other options XOS 7 : 1 > Any clues? Anything info I can provide to help debug this? I think there are fewer problems if I _first_ start multiprocessing, _then_ create a swank-server, then use slime-connect from emacs. But that's not nearly as convenient as just typing M-x slime. :-)

2 1

[slime-devel] slime-input-stream and REPL extensions
by Christian Lynbech 21 Jan '04

21 Jan '04

Would it be possible to change `slime-input-stream' to become a real stream rather than just a struct? As a non-stream struct it tends to wreak havoc when some non-slime aware code tries to operate on *standard-input*. My concrete problem is with Paul Foleys (mycroft(a)actrix.gen.nz) repl-ext package that allows one to do Allegro style repl commands, and I have come to absolutely love this. This wants to replace the toplevel REPL but does not know how to handle slime-input-streams. The fix is rather simple, but I think it would make slime more robust if it would not be necessary to fix all packages that needs to operate on *standard-input* one by one. Obviously, I have no idea how difficult such a thing would be, but it may be worth keeping in the back of your heads :-) Another thing would be to consider integrating repl-ext into slime, it is really nice, IMHO. ------------------------+----------------------------------------------------- Christian Lynbech | christian #\@ defun #\. dk ------------------------+----------------------------------------------------- Hit the philistines three times over the head with the Elisp reference manual. - petonic(a)hal.com (Michael A. Petonic)

2 2

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

21 Jan '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.226 slime/ChangeLog:1.230 --- slime/ChangeLog:1.226 Mon Jan 19 16:49:49 2004 +++ slime/ChangeLog Tue Jan 20 16:53:15 2004 @@ -1,3 +1,18 @@ +2004-01-20 Lasse Rasinen <lrasinen(a)iki.fi> + + * slime.el (slime-prin1-to-string): Replacement for + prin1-to-string that avoids escaping non-ascii characters in a + way that the CL reader doesn't understand. Allows use of 8-bit + characters in Lisp expressions with Emacs in unibyte-mode. + +2004-01-20 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-eval-print-last-expression): Insert a newline + before and after the result. + (slime-easy-menu): Added menu items: + "Eval Region", "Scratch Buffer", "Apropos Package..." + Added some bold to default SLDB faces. + 2004-01-19 Alan Ruttenberg <alanralanr(a)comcast.net> *swank-openmcl.lisp in frame-catch-tags, ppc32::catch-frame.catch-tag-cell -> 0, ppc32::catch-frame.csp-cell -> 3. FIXME when this code is more stable in openMCL.

1 0