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

[slime-devel] pdfTeX failage on Slime manual
by Brian Downing 29 Jun '04

29 Jun '04

I just ran into the same stack overflow that's happening in Slime's manual on some of my own stuff. It turns out what my problem was is that pdfTeX really does not like whatever it is that TeXinfo generates for @macro output living in chapter and section titles. If I replaced my @FOOBAR{} with @acronym{FOOBAR} - only in chapter and section titles - it ran through fine. If I had to make a wild guess why this fails on pdfTeX and not plain TeX, it would be that pdfTeX is stuffing the section headers into the PDF file as the bookmark tree. -bcd -- *** Brian Downing <bdowning at lavos dot net>

2 1

[slime-devel] Feature Request: Generic Function Browser
by Thomas Schilling 29 Jun '04

29 Jun '04

Is there already a SLIME feature like a "Generic Function Browser"? If so can someone tell how to invoke it? Here's what I'd expect from it: - list all methods of a generic function in a separate buffer - by navigating to a function and pressing 'r' it gets removed (like with REMOVE-METHOD) - 'q' closes the window - there might be some other nice things possible but this is what's be most important, cause every time I modify a method the old method is still there and it's awfully complicated to remove it then. hope someone can help -ts -- ,, \../ / <<< The LISP Effect |_\\ _==__ __ | |bb| | _________________________________________________

2 1

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

29 Jun '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.431 slime/ChangeLog:1.436 --- slime/ChangeLog:1.431 Sun Jun 27 08:23:54 2004 +++ slime/ChangeLog Mon Jun 28 14:05:28 2004 @@ -1,3 +1,77 @@ +2004-06-28 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (slime-doc-map): New keymap for documentation + commands. These all use the `C-c C-d' prefix, followed by: + a - apropos + p - apropos-package + z - apropos-all + d - describe-symbol + f - describe-function + h - hyperspec lookup + ~ - hyperspec lookup of a format character + The final keystroke is bound both unmodified and with control, so + both `C-c C-d a' and `C-c C-d C-a' will make an apropos + search. The exception is hyperspec-lookup, because it's nice to + leave C-h unbound so that `C-c C-d C-h' will summarise the + documentation bindings. + +2004-06-28 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * swank-allegro.lisp (nth-frame): Skip frames where + frame-visible-p is false. + + * slime.el (slime-buffer-package): Return the cached package if + can't something more sensible; this reverts a previous change. + The Lisp side will now fall back to an existing package if the one + supplied by Emacs doesn't exist. Using the cached version is also + necessary for some commands in the apropos buffer. + (sldb-insert-frame): Set the default-action property; pressing RET + on frame lines now shows/hides details. + (sldb-toggle-details): Preserve the current column. + (slime-inspector-buffer, slime-saved-window-config) + (slime-inspector-quit): Save and restore the window configuration. + (slime-highlight-suppressed-forms, slime-search-suppressed-forms): + Display expressions with reader conditionals (#+/#-) where the + test is false in font-lock-comment-face. No implemented for + XEmacs. + (repl-return): New test. + +2004-06-28 Luke Gorrie <luke(a)bluetail.com> + + * slime.el: Events in the *slime-events* buffer are now exact + on-the-wire messages, without including e.g. Elisp continuation + functions. This is easier for debugging I think. + + * swank-allegro.lisp (compute-backtrace): Only include frames + satisfying `debugger:frame-visible-p'. I did this as a lame + workaround for a problem where `output-frame' was segfaulting on + certain frames, and those frames happened not to be visible-p. I + don't know if it really fixes anything. + + * hyperspec.el (common-lisp-hyperspec-format): This command now + works at the end of the buffer, fixed `char-after' usage as + suggested by Johan Bockgård. + +2004-06-28 Christophe Rhodes <csr21(a)cam.ac.uk> + + * hyperspec.el: add support for issue cross-reference lookups, + strongly inspired by hyperspec symbol lookup. + (common-lisp-hyperspec-issuex-table, + common-lisp-hyperspec-issuex-symbols): new variables + (common-lisp-issuex): new function + + * slime.el (sldb-format-reference-node, sldb-lookup-reference): + (sldb-reference-properties): use new support for issue lookups + to support :ansi-cl :issue reference types. + + * hyperspec.el: add support for glossary lookups. + (common-lisp-glossary-fun): new variable + (common-lisp-glossary-4.0, common-lisp-glossary-6.0): new functions + + * slime.el (sldb-format-reference-node, sldb-lookup-reference): + (sldb-reference-properties): use new support for glossary lookupts + to support :ansi-cl :glossary reference types. + 2004-06-27 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * doc/slime.texi: Remove macros from chapter and section headings @@ -59,7 +133,7 @@ 2004-06-24 Brian Downing <bdowning(a)lavos.net> - * slime.el (slime-repl-send-input): Fixed a subtle difference in + * slime.el (slime-repl-send-input): Fixed a subtle difference in sending input to the Lisp introduced in 1.316. The newline was not getting sent, resulting in the Lisp constantly asking for more read data. I believe the code has been adjusted to behave the

1 0

[slime-devel] Allegro 6.2 problem
by Peter Seibel 28 Jun '04

28 Jun '04

This may be related to the thing Edi mentioned the other day. Anyway, I start SLIME using Allegro 6.2 on Linux. Initially I'm in the directory where test-debug.lisp lives: ; SLIME: The Superior Lisp Interaction Mode for Emacs CL-USER> CL-USER> (compile-file "test-debug.lisp") ;;; Compiling file test-debug.lisp ;;; Writing fasl file test-debug.fasl ;;; Fasl write complete #p"test-debug.fasl" NIL NIL So far so good. Now I ,change-directory up one directory and try again. Which should fail since the file won't be found. But it doesn't just fail; in the SLIME repl window I get the following: CL-USER> CL-USER> (compile-file "test-debug.lisp") Error: Received signal number 11 (Segmentation violation) [condition type: SYNCHRONOUS-OPERATING-SYSTEM-SIGNAL] Restart actions (select using :continue): 0: Prompt for a different filename to compile 1: Abort handling SLIME request. 2: Abort entirely from this process. [Current process: repl-thread] [1] CL-USER(1): Typing Allegro commands (e.g. :cont 1) doesn't seem to do anything. C-c C-c gets me into sldb where I can use one of the ABORT restarts to get back to the main REPL. But this seems wrong. -Peter -- Peter Seibel peter(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

3 5

[slime-devel] Precision of 'v' in SLDB on SBCL
by Luke Gorrie 28 Jun '04

28 Jun '04

Ahoy, I had thought the 'view-source' command only worked at defun-granularity in SBCL, but Christophe just pointed out that it works to the exact expression (like in CMUCL) provided that your code is compiled at (optimize (debug 2)) or higher. Good to know :-) Unofficially you can make (debug 2) the global default with this in your ~/.sbclrc: (setf (cdr (assoc 'sb-c::debug sb-c::*policy*)) 2) -Luke

2 1

[slime-devel] Sorting contributors by last name
by Michael Weber 28 Jun '04

28 Jun '04

Hi, attached is a small patch which sorts the Contributors section in the slime docs by last name. Of course it is a heuristic (uses last _word_ as main sorting key), but it works for non-funky cases. (Patch is attached.) On request I can get rid of the AWK dependency (from texinfo-tabulate.awk), but my replacement sed expression does not exactly make the whole thing look prettier (though it is rather short), so I'd leave it for now. I resisted trying to do the sorting with sed, so perhaps there is still hope for me... :) Cheers, Michael

5 11

[slime-devel] SLIME User Survey
by Luke Gorrie 28 Jun '04

28 Jun '04

If the ALU can do it then so can we :-). It would be nice to get some feedback to understand which backends are getting the most/least usage and which ones are flaky. So if you are an active SLIME user and you have a moment then please reply to this mail (send the reply to the list). Questions: Which Lisp versions do you use SLIME with? Which Emacs versions? How well does SLIME work for you? What bugs (reproducible or otherwise) or missing features annoy you? 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? If you said anything negative above then please say something nice here to make us feel good:

36 65

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

28 Jun '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.429 slime/ChangeLog:1.431 --- slime/ChangeLog:1.429 Fri Jun 25 03:13:40 2004 +++ slime/ChangeLog Sun Jun 27 08:23:54 2004 @@ -1,3 +1,28 @@ +2004-06-27 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * doc/slime.texi: Remove macros from chapter and section headings + to avoid texi2pdf breakage. + + * swank-source-path-parser.lisp (cmucl-style-get-macro-character): + Add tests for #\space and #\\. Suggested by Christophe Rhodes. + + * swank-sbcl.lisp, swank-openmcl.lisp, swank-lispworks.lisp, + swank-cmucl.lisp, swank-backend.lisp, swank-allegro.lisp, + swank-abcl.lisp (thread-id, find-thread): New backend functions. + + * swank.lisp (dispatch-event): Quitting from the debugger was + seriously broken. Fix it. Move generation of thread ids to the + backends. + (encode-message, send-to-socket-io): Use WITHOUT-INTERRUPTS in + send-to-socket-io. The multithreaded version of encode-message + doesn't need it. + (nth-thread): Renamed from lookup-thread-by-id. + (debug-nth-thread): Renamed from debug-thread-by-id: + (kill-nth-thread): Renamed from kill-thread-by-id. + + * slime.el (sldb-get-buffer): Add support for sldb buffers for + multiple threads. + 2004-06-25 Thomas F. Burdick <tfb(a)OCF.Berkeley.EDU> * swank-sbcl.lisp (call-with-syntax-hooks, with-debootstrapping):

1 0

[slime-devel] Tiny annoynace - view-mode
by Brian Downing 28 Jun '04

28 Jun '04

I like to use view mode to page through files while browsing code. It's really easy to get to via dired as well ('v'). However, when viewing a Lisp file from dired like that, slime-mode wins on the binding for SPC, so pressing space gets you 'Buffer is read-only' instead of scrolling down. -bcd

1 0

[slime-devel] Package profiling in SBCL
by Constantine Vetoshev 27 Jun '04

27 Jun '04

I noticed PROFILE-PACKAGE isn't implemented for SBCL. SBCL's native SB-PROFILE:PROFILE does support package-level profiling given a string argument. It has an interface somewhat like the one SLIME expects: it unprofiles and reprofiles already-profiled functions, although it does not support CALLERS-P or METHODS; I suppose that's why it isn't in the SBCL backend now. Even with this limitation, I find these patches useful: Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.308 diff -r1.308 slime.el 4148,4149c4148,4151 < (y-or-n-p "Record the most common callers? ") < (y-or-n-p "Profile methods? "))) --- > (unless (string-match "sbcl" inferior-lisp-program) > (y-or-n-p "Record the most common callers? ")) > (unless (string-match "sbcl" inferior-lisp-program) > (y-or-n-p "Profile methods? ")))) Index: swank-sbcl.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-sbcl.lisp,v retrieving revision 1.85 diff -r1.85 swank-sbcl.lisp 534a535,541 > ;;; FIXME: This does not meaningfully support CALLERS-P or METHODS. > (defimplementation profile-package (package callers-p methods) > (when package > (let ((package-name (string-upcase package))) > (eval `(sb-profile:profile ,package-name)))) > (format nil "Profiling all functions in package ~A." package)) > Out of curiosity, are there any plans to use the included metering.lisp facility for all Lisp implementations, and not just CLISP? The current profiling hooks in SLIME expect a CMUCL-like interface, and supporting, e.g., the native profiler in Allegro CL would require either changing the front end (functions in slime.el need to ask different questions and provide different report options) or resorting to low-level hackery to make the other Lisps' profilers look like CMUCL's. -- Regards, Constantine Vetoshev

1 0