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

[slime-devel] clhs-lookup for reader macros
by Stas Boukarev 27 Feb '09

27 Feb '09

I added reader macros for hyperspec-lookup, hope this would be useful. -- With Best Regards, Stas.

2 1

[slime-devel] Problem with truncation of strings in debugger
by Jeff Workman 26 Feb '09

26 Feb '09

When I evaluate (format t "~A" (some-str-function)) on a longish string in debugger with E, the string is printed truncated, which seems like the wrong behavior to me. Also, surprisingly when I evaluate (setf *str* (some-str-function)) from debugger, the string stored in *str* is truncated as well. That suggests to me that the debugger is modifying the behavior of (format nil ...) or other functions I use in constructing strings used internally in my program, which would obviously be very bad and could interfere with operation of the program. I'm using SBCL 1.0.20 on Linux (and cvs slime) btw.

3 3

[slime-devel] Inspector doc
by Madhu 17 Jan '09

17 Jan '09

Helu, I'm having trouble using the inspector effectively: some objects are truncated, some lists are truncated etc. These boil down to bindings of printer variables [the debug state, etc] Can the inspector related variables be documented, and the rationale spelt out as to which output is being truncated, why, and under what circumstances? Could the hardcoded constants be documented as being hardcoded? I suspect this is not too much to ask if the new inspector is a "better thought out" replacement, the design could be explained in a few paragraphs in comments in the code or in a separate doc. I think it is an important enough component of SLIME to define the behaviour outside of the code which implements it. -- Madhu

4 8

[slime-devel] request for pecifying location fasl-files
by Knut Olav Bøhmer 10 Jan '09

10 Jan '09

Hi, I would like to be able to specify where slime should place it's fasl-files when running slime-compile-and-load-file. The location should be per-buffer/filename configurable by placing variable-definition in the header of a .lisp file or by a hook that runs when a .lisp file is opened. I have attached an example implementation that I use, and have used for a long time. It works for me. -- Free Software Consultant Cell: +47 - 47 34 40 08 Phone: +47 - 21 53 69 00, Fax: +47 - 21 53 69 09 Addr: Nydalsveien 30b, 0484 Oslo <http://www.freecode.no/>

5 4

[slime-devel] Problems with slime using sbcl on winXP (emacsW32)
by Matthew D. Swank 06 Dec '08

06 Dec '08

Starting in late September, whenever I try to exit out of the debugger the repl prompt doesn't come back. Example: *slime-repl sbcl* CL-USER> o *sldb sbcl/0* The variable O is unbound. [Condition of type UNBOUND-VARIABLE] Restarts: 0: [RETRY] Retry SLIME REPL evaluation request. 1: [ABORT] Return to SLIME's top level. <-----------pick this one 2: [CLOSE-CONNECTION] Close SLIME connection 3: [ABORT] Exit debugger, returning to top level. The repl buffer comes back with no prompt, and all further requests are pipelined. This does not happen in clisp. Some other info: *slime-events* (:emacs-rex (swank:listener-eval "o\n") "COMMON-LISP-USER" :repl-thread 14) (:debug 0 1 ("The variable O is unbound." " [Condition of type UNBOUND-VARIABLE]" nil) (("RETRY" "Retry SLIME REPL evaluation request.") ("ABORT" "Return to SLIME's top level.") ("CLOSE-CONNECTION" "Close SLIME connection") ("ABORT" "Exit debugger, returning to top level.")) ((0 "(SB-INT:SIMPLE-EVAL-IN-LEXENV O #<NULL-LEXENV>)") (1 "(SWANK::EVAL-REGION \"o\\n\")") (2 "((LAMBDA ()))") (3 "(SWANK::TRACK-PACKAGE #<CLOSURE (LAMBDA #) {25B5C3E5}>)") (4 "(SWANK::CALL-WITH-RETRY-RESTART \"Retry SLIME REPL evaluation request.\" #<CLOSURE (LAMBDA #) {25B5C375}>)") (5 "(SWANK::CALL-WITH-BUFFER-SYNTAX NIL #<CLOSURE (LAMBDA #) {25B5C35D}>)") (6 "(SWANK::REPL-EVAL \"o\\n\")") (7 "(SB-INT:SIMPLE-EVAL-IN-LEXENV (SWANK:LISTENER-EVAL \"o\\n\") #<NULL-LEXENV>)") (8 "(SWANK::EVAL-FOR-EMACS (SWANK:LISTENER-EVAL \"o\\n\") \"COMMON-LISP-USER\" 14)") (9 "(SWANK::PROCESS-REQUESTS NIL)") (10 "((LAMBDA ()))") (11 "((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {241035BD}>)") (12 "(SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {2401F269}> #<CLOSURE (LAMBDA #) {241035CD}>)") (13 "(SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {2401F269}> #<CLOSURE (LAMBDA #) {241035BD}>)") (14 "(SWANK::HANDLE-REQUESTS #<SWANK::CONNECTION {2401F269}> NIL)") (15 "((LAMBDA ()))") (16 "((LAMBDA (SWANK-BACKEND::HANDLER FUNCTION)) #<FUNCTION (LAMBDA #) {23DC867D}> #<CLOSURE (LAMBDA #) {24103555}>)") (17 "(SWANK::SIMPLE-SERVE-REQUESTS #<SWANK::CONNECTION {2401F269}>)") (18 "(SWANK::SERVE-CONNECTION #<SB-BSD-SOCKETS:INET-SOCKET descriptor -1 {23FB59F9}> NIL NIL :ISO-8859-1)") (19 "(SWANK::SETUP-SERVER 0 #<CLOSURE (LAMBDA #) {23F4527D}> NIL NIL :ISO-8859-1)")) (14)) (:debug-activate 0 1 nil) (:emacs-rex (swank:invoke-nth-restart-for-emacs 1 1) nil 0 15) (:return (:abort) 15) (:debug-return 0 1 nil) These are the current contribs I'm using: (require 'slime-fancy) (require 'slime-asdf) Just using straight socket for communication: swank:*communication-style* => nil Matt -- "You do not really understand something unless you can explain it to your grandmother." -- Albert Einstein.

3 7

[slime-devel] Reincarnate "eval..."
by Gábor Melis 02 Dec '08

02 Dec '08

Running cvs HEAD I now realize that I grew to rely on checking the modeline of lisp buffers to see whether there are outstanding requests. Often, I start evalutations that take minutes or hours to finish and it's useful to have this at a glance without having to worry about missing when the return value is printed or having to check the running threads. The attached patch does not reinstate "eval...", instead it displays the number of outstanding requests like "CON:sbcl{3}" if it's greater than zero. Currently there is a loop through buffer-list, it that's a problem maybe there is a better way to arrange for the modeline to be updated using a global mode-line-format variable as a trigger to signal the change in connection-state that is to be recomputed in each slime buffer. The patch does not solve the minor problems caused by the use of run-with-idle-timer, namely that the modeline may not be updated if the status of the connection changes in the background while emacs is idle. Cheers, Gábor

3 3

[slime-devel] Call stack when using Lisp debugger from sldb
by Raymond Toy 01 Dec '08

01 Dec '08

Sometimes when I'm in sldb, I want to use the actual Lisp debugger because sometimes it more convenient to have a real repl. Pressing B works nicely. Previously, however, I would be in the debugger, and the backtrace would be exactly what I expected, with the top of stack being exactly where the error occurred. Now, however, the actual error is some 10-20 frames away because there are lots of slime things in between. This is kind of nice too because now I can return to sldb, which I couldn't before. But this also means I now have to go hunt around for the real offending frame. Is there a way to the old behavior? Ray

3 5

[slime-devel] Daily ChangeLog diff
by Helmut Eller 30 Nov '08

30 Nov '08

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.141 slime/contrib/ChangeLog:1.142 --- slime/contrib/ChangeLog:1.141 Sat Nov 22 12:19:26 2008 +++ slime/contrib/ChangeLog Sat Nov 29 11:12:39 2008 @@ -1,3 +1,9 @@ +2008-11-29 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime-package-fu.el (slime-goto-package-source-definition): + `(slime-pop-to-location loc 'excursion)' no longer exists; use + `(slime-goto-source-location loc)' instead. + 2008-11-22 Geoff Wozniak <geoff(a)wozniak.ca> * swank-c-p-c.lisp (parse-completion-arguments): Change the

1 0

[slime-devel] slime-package-fu.el
by Stas Boukarev 29 Nov '08

29 Nov '08

slime-export-symbol-at-point doesn't work: it calls slime-pop-to-location with argument 'excursion, which it no longer accepts. Though if i change it to 'frame or 'window, it still doesn't work properly. -- With Best Regards, Stas.

2 2

[slime-devel] Daily ChangeLog diff
by Helmut Eller 24 Nov '08

24 Nov '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1586 slime/ChangeLog:1.1587 --- slime/ChangeLog:1.1586 Sat Nov 22 22:36:40 2008 +++ slime/ChangeLog Sun Nov 23 22:11:36 2008 @@ -1,3 +1,18 @@ +2008-11-23 Helmut Eller <heller(a)common-lisp.net> + + `q' in temp buffers should only delete the window if it was newly + created for the buffer. + + * slime.el (slime-display-popup-buffer): New function. Recognize + if the window didn't exist before. Save the created window and + the selected window in buffer local variables. + (slime-make-popup-buffer): Renamed from slime-popup-buffer. + (slime-popup-buffer-quit): Delete the created window (if needed) + and restore the old selected window. Don't touch other windows. + + (slime-edit-value-callback): Calling lisp-mode deletes all local + variables. We need to that inside with-popup-buffer. + 2008-11-22 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-update-all-modelines): Only walk through

1 0