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

[slime-devel] comma shortcut doesn't work always
by Edi Weitz 31 Jan '06

31 Jan '06

Another minor glitch that I encountered is that the comma shortcut in the REPL doesn't always work. I can consistently reproduce it (GNU Emacs 21.3.50 and also 21.3 release) like this: 1. Make sure point is at the beginning of a REPL input line. 2. Split Emacs frame into two windows, one of them being the REPL the other one containing something else. 3. Hide REPL window with C-x 0. 4. Now type M-x slime. 5. Type the comma. At this point I'm not asked for a shortcut command in the minibuffer but the comma is simply entered into the REPL instead. Anybody else seeing this? Cheers, Edi.

10 25

Re: [slime-devel] Re: CLISP SLIME implementation breaks in CVS
by Bill_Clementson＠peoplesoft.com 21 Jan '06

21 Jan '06

Luke Gorrie <luke(a)bluetail.com> writes: > Bill_Clementson(a)peoplesoft.com writes: > > > My previous SLIME installation was a CVS install from 4/18. I've just taken > > the latest CVS install and the CLISP SLIME implementation (under Windows) > > breaks. Here is the error: > > > > COERCE: #<MACRO #<COMPILED-CLOSURE SWANK::DEFSLIMEFUN>> cannot be coerced > > to type FUNCTION > > [Condition of type SIMPLE-TYPE-ERROR] > > I can reproduce this but I've no idea what is causing it. It /looks/ > like someone is trying to call defslimefun as a function rather than a > macro, but I don't see where it could happen -- the macro is declared > at the top of the only file that refers to it. > > I did fix a different but similar problem that I got under CLISP. It > seems like I had to swap the order of a couple of macros, one of which > expanded into into code that calls the other, but that surely can't be > the reason. > > > Backtrace: > > 0: EVAL frame for form (SWANK:CREATE-SWANK-SERVER 4007) > > Mine actually gives an empty backtrace (!). I fixed the Elisp-side to > handle that incase it helps someone more CLISP-savvy find the problem. Has anybody had any luck in finding the source of this problem? CLISP still breaks for me in the latest CVS. I have had a look at all of the DEFSLIMEFUN's that were modified since 4/18 (the previous CVS version that I had which was working ok with CLISP) and haven't found any obvious clues. Any suggestions on how I might debug this issue as it occurs at startup during the slime-connect processing in Emacs (after CLISP has started up successfully)? - Bill

5 6

[slime-devel] A command for M-q
by Thomas F. Burdick 18 Jul '04

18 Jul '04

I missed being able to do M-q to reindent the current defun, like in ILISP. Here's the version I'm using. The patch is against a month-old cvs snapshot, sorry. --- slime.el.~1.258.~ Thu Apr 8 16:41:04 2004 +++ slime.el Sun May 2 17:02:35 2004 @@ -449,6 +449,7 @@ ("\M-." slime-edit-definition :inferior t :sldb t) ("\M-," slime-pop-find-definition-stack :inferior t :sldb t) ("\C-q" slime-close-parens-at-point :prefixed t :inferior t) + ("\M-q" slime-reindent-defun :inferior t) ;; Evaluating ("\C-x\C-e" slime-eval-last-expression :inferior t) ("\C-x\M-e" slime-eval-last-expression-display-output :inferior t) @@ -5523,6 +5524,29 @@ (get symbol 'slime-indent)) (put symbol 'slime-indent indent) (put symbol 'common-lisp-indent-function indent))))) + +(defun slime-reindent-defun (&optional force-text-fill) + "Reindent the current defun, or refill the current paragraph. +If point is inside a comment block, the text around point will be +treated as a paragraph and will be filled with `fill-paragraph'. +Otherwise, it will be treated as Lisp code, and the current defun +will be reindented. If the current defun has unbalanced parens, +an attempt will be made to fix it before reindenting. + +When given a prefix argument, the text around point will always +be treated as a paragraph. This is useful for filling docstrings." + (interactive "P") + (save-excursion + (if (or force-text-fill (slime-beginning-of-comment)) + (fill-paragraph nil) + (let ((start (progn (beginning-of-defun) (point))) + (end (ignore-errors (end-of-defun) (point)))) + (unless end + (forward-paragraph) + (slime-close-all-sexp) + (end-of-defun) + (setf end (point))) + (indent-region start end))))) ;;; Test suite

2 3

[slime-devel] indent and autocomplete
by Eric Blood 16 Jul '04

16 Jul '04

The attached patch creates the option of having the naked Tab key do both indent and autocomplete as it currently does in the repl. I moved and renamed slime-repl-indent-and-complete-symbol to slime-indent-and-complete-symbol since it is not repl specific. Also, I have added more default options for the typeout frame--specifically it now has a default width, and moves the typeout frame to the upper right. -- eblood Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.309 diff -u -w -r1.309 slime.el --- slime.el 8 Jun 2004 23:58:09 -0000 1.309 +++ slime.el 9 Jun 2004 04:44:28 -0000 @@ -135,6 +135,10 @@ (defvar slime-kill-without-query-p t "If non-nil, kill Slime processes without query when quitting Emacs.") +(defvar slime-tab-indent-and-complete-p t + "Whether the TAB key should do both an indent and autocomplete in the +Slime minor mode.") + (defvar slime-sbcl-manual-root "http://www.sbcl.org/manual/" "*The base URL of the SBCL manual, for documentation lookup.") @@ -553,7 +557,10 @@ (define-key inferior-slime-mode-map [(control return)] 'inferior-slime-closing-return) (define-key inferior-slime-mode-map - [(meta control ?m)] 'inferior-slime-closing-return)) + [(meta control ?m)] 'inferior-slime-closing-return) + (when slime-tab-indent-and-complete-p + (slime-define-key "\C-i" 'slime-indent-and-complete-symbol + :inferior t))) (slime-init-keymaps) @@ -1033,6 +1040,18 @@ (when (buffer-live-p (get-buffer buffer-name)) (kill-buffer buffer-name))) +(defun slime-indent-and-complete-symbol () + "Indent the current line and perform symbol completion. +First indent the line. If indenting doesn't move point complete the +symbol." + (interactive) + (let ((pos (point))) + (lisp-indent-line) + (when (and (= pos (point)) + (save-excursion + (re-search-backward "\\(\\s_\\|\\sw\\)+\\=" nil t))) + (slime-complete-symbol)))) + (defmacro slime-with-rigid-indentation (level &rest body) "Execute BODY and then rigidly indent its text insertions. Assumes all insertions are made at point." @@ -2330,18 +2349,6 @@ (insert "\n") (lisp-indent-line))) -(defun slime-repl-indent-and-complete-symbol () - "Indent the current line and perform symbol completion. -First indent the line. If indenting doesn't move point complete the -symbol." - (interactive) - (let ((pos (point))) - (lisp-indent-line) - (when (and (= pos (point)) - (save-excursion - (re-search-backward "\\(\\s_\\|\\sw\\)+\\=" nil t))) - (slime-complete-symbol)))) - (defun slime-repl-delete-current-input () (delete-region slime-repl-input-start-mark slime-repl-input-end-mark)) @@ -2490,7 +2497,7 @@ ("\C-c:" 'slime-interactive-eval) ("\C-c\C-e" 'slime-interactive-eval) ;("\t" 'slime-complete-symbol) - ("\t" 'slime-repl-indent-and-complete-symbol) + ("\t" 'slime-indent-and-complete-symbol) (" " 'slime-space) ("\C-\M-x" 'slime-eval-defun) ("\C-c\C-o" 'slime-repl-clear-output) @@ -3565,7 +3572,8 @@ "The current typeout window.") (defvar slime-typeout-frame-properties - '((height . 16) (minibuffer . nil) (name . "SLIME Typeout")) + '((width . 40) (height . 10) (minibuffer . nil) + (left . -10) (top . 10) (name . "SLIME Typeout")) "The typeout frame properties (passed to `make-frame').") (defun slime-typeout-active-p () @@ -3637,7 +3645,7 @@ (slime-complete-restore-window-configuration)) ((memq this-command '(self-insert-command slime-complete-symbol - slime-repl-indent-and-complete-symbol + slime-indent-and-complete-symbol backward-delete-char-untabify backward-delete-char scroll-other-window))

3 2

[slime-devel] Symbols in COMMON-LISP are all in UPPER CASE!
by Pascal J.Bourguignon 30 Jun '04

30 Jun '04

Symbols in COMMON-LISP are all in upper case. (Yes, I know, it's a little known fact about COMMON-LISP). So why can't we look up them in upper case? Let's ignore case when completing symbols in slime-hyperspec-lookup and everybody will be happy. (defun slime-hyperspec-lookup (symbol-name) "A wrapper for `hyperspec-lookup'" (interactive (list (let ((completion-ignore-case t) ;; <<<<--------- (symbol-at-point (slime-symbol-name-at-point))) (if (and symbol-at-point (intern-soft (downcase symbol-at-point) common-lisp-hyperspec-symbols)) symbol-at-point (completing-read "Look up symbol in Common Lisp HyperSpec: " common-lisp-hyperspec-symbols #'boundp t symbol-at-point 'common-lisp-hyperspec-history))))) (hyperspec-lookup symbol-name)) -- __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

5 5

[slime-devel] The 1.0-alpha plan
by Luke Gorrie 30 Jun '04

30 Jun '04

Ahoy, I checked in a mkdist.sh shell script for creating a distribution. I made a "fake" release called 1.0alpha0 with it here: http://www.bluetail.com/~luke/misc/lisp/slime-1.0alpha0.tar.gz That's not a real release for distribution, just an example to see if we're missing anything. Two things that I know need doing before releasing an alpha tarball: Update the manual a bit - I'm on it. Write release notes. I've made a start in the NEWS file. It would be great if people could contribute notes about our ACL/CLISP/ABCL backends, and anything important I've missed about the others (e.g. what's the oldest LispWorks what we actually work with?) Is there anything else? If not, I was thinking of making an alpha1 tarball tomorrow or the next day and releasing it. -Luke

4 6

[slime-devel] long delay starting up slime on a computer off-line
by Chisheng Huang 30 Jun '04

30 Jun '04

When my computer is connected to the internet, M-x slime will get me a slime repl buffer immediately. However, if my computer is not connected to the internet, it takes much longer to get a slime repl buffer. There is a long wait while the mini buffer displaying "Connecting to Swank on port 35948...", after which there is another long wait while the mini buffer displaying "initial handshake...". The first delay is due to a call to OPEN-NETWORK-STREAM in SLIME-NET-CONNECT. Not sure about the 2nd delay, which is probably on the CL side. Is it possible to get rid of this long delay when starting up Slime on a computer off-line? Best, -cph

2 3

[slime-devel] changing slime-keys
by Pascal J.Bourguignon 30 Jun '04

30 Jun '04

What function should I call when I change slime-keys to have them taken into account immediately? -- __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

3 5

[slime-devel] Patch: show the current debug level in the REPL
by Thomas F. Burdick 30 Jun '04

30 Jun '04

Below is a patch to show the current debug level in the REPL, when it's > 0 Index: ChangeLog =================================================================== RCS file: /project/slime/cvsroot/slime/ChangeLog,v retrieving revision 1.443 diff -u -F^(def -r1.443 ChangeLog --- ChangeLog 29 Jun 2004 22:07:00 -0000 1.443 +++ ChangeLog 30 Jun 2004 04:23:33 -0000 @@ -1,3 +1,10 @@ +2004-06-29 Thomas Burdick <tfb(a)OCF.Berkeley.EDU> + + * slime.el: Indicate when the REPL is in the debugger's context + (slime-debug-level): new connection var + (slime-dispatch-event): set slime-debug-level to match *sldb-level* + (slime-repl-insert-prompt): show debug-level in prompt when > 0 + 2004-06-30 Luke Gorrie <luke(a)bluetail.com> * NEWS: Wrote preliminary release notes for alpha-1. Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.346 diff -u -F^(def -r1.346 slime.el --- slime.el 29 Jun 2004 20:17:05 -0000 1.346 +++ slime.el 30 Jun 2004 04:23:46 -0000 @@ -1561,6 +1561,9 @@ (defmacro slime-def-connection-var (varn (slime-def-connection-var slime-use-sigint-for-interrupt nil "If non-nil use a SIGINT for interrupting.") +(slime-def-connection-var slime-debug-level 0 + "The current level of recursive debugging.") + ;; XXX pending continuations are not removed if Lisp crashes. @@ -1602,9 +1605,11 @@ (defun slime-dispatch-event (event &opti (sldb-activate thread level)) ((:debug thread level condition restarts frames) (assert thread) + (setf (slime-debug-level) level) (sldb-setup thread level condition restarts frames)) ((:debug-return thread level) (assert thread) + (setf (slime-debug-level) (1- level)) (sldb-exit thread level)) ((:emacs-interrupt thread) (cond ((slime-use-sigint-for-interrupt) (slime-send-sigint)) @@ -2168,7 +2173,9 @@ (defun slime-repl-insert-prompt (result (slime-insert-propertized '(face slime-repl-result-face) result) (unless (bolp) (insert "\n")) (let ((prompt-start (point)) - (prompt (format "%s> " (slime-lisp-package)))) + (prompt (if (> (slime-debug-level) 0) + (format "%s [%d]> " (slime-lisp-package) (slime-debug-level)) + (format "%s> " (slime-lisp-package))))) (slime-propertize-region '(face slime-repl-prompt-face read-only t

5 5

[slime-devel] Fedora Core 2 and doc build
by Dan Pierson 30 Jun '04

30 Jun '04

For some reason 'sort -d' either loops forever or takes a VERY long time on Fedora Core 2. This breaks the docs build. Removing the -d fixes it for me, as in the following patch, but there may have been some good reason for using the switch... Index: Makefile =================================================================== RCS file: /project/slime/cvsroot/slime/doc/Makefile,v retrieving revision 1.4 diff -u -r1.4 Makefile --- Makefile 22 Jun 2004 14:06:56 -0000 1.4 +++ Makefile 30 Jun 2004 14:02:30 -0000 @@ -43,7 +43,7 @@ contributors.texi: ../ChangeLog Makefile texinfo-tabulate.awk cat ../ChangeLog | \ sed -ne '/^[0-9]/{s/^[^ ]* *//; s/ *<.*//; p;}' | \ - sort -d | \ + sort | \ uniq -c | \ sort -nr| \ sed -e 's/^[^A-Z]*//' | \

2 1

[slime-devel] Symbol's value as variable is void: slime-net-processes while starting SLIME
by Paolo Amoroso 30 Jun '04

30 Jun '04

I have updated my working copy of the CVS sources a couple of hours ago, and SLIME does no longer work. It worked fine the previous time I had updated the sources, i.e. yesterday or at most a couple of days ago. More specifically, when I issue the `M-x slime' command from Emacs, I get the error: Error in init file: Symbol's function definition is void: slime-def-connection-var I also get this error in another circumstance: Symbol's value as variable is void: slime-net-processes Things are screwed so bad that when I run Gnus, it correctly accesses news, but fails to get mail from my local spool. This, anyway, is no big deal: Gnus and the rest work fine if I disable SLIME-related forms in my ~/.emacs file. Before starting SLIME, I made sure to delete all existing fasl files. I use GNU Emacs 20.7.2 and CMUCL 18e under Debian Woody. I just thought you might be interested in this... :) Paolo "SLIME CVS head or bust" Amoroso -- Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film

1 0

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

30 Jun '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.436 slime/ChangeLog:1.443 --- slime/ChangeLog:1.436 Mon Jun 28 14:05:28 2004 +++ slime/ChangeLog Tue Jun 29 15:07:00 2004 @@ -1,3 +1,37 @@ +2004-06-30 Luke Gorrie <luke(a)bluetail.com> + + * NEWS: Wrote preliminary release notes for alpha-1. + +2004-06-29 Luke Gorrie <luke(a)bluetail.com> + + * mkdist.sh: New shell script for creating a tarball for + distribution. + +2004-06-29 Bill Clementson <Bill_Clementson(a)peoplesoft.com> + + * slime.el (slime-who-map): Add extra bindings for the XREF + commands as with the documentation commands. Now `C-c C-w C-c' is + `slime-who-calls' in addition to `C-c C-w c', etc. + +2004-06-29 Luke Gorrie <luke(a)bluetail.com> + + * slime.el (sldb-prune-initial-frames): Tweaked regexp for + matching SWANK's own stack frames for effectiveness in SBCL. + (slime-keys): Shadow remaining inf-lisp keys (C-c C-a, C-c C-v) + with a null `slime-nop' command until we put them to a real use. + + * swank.lisp (open-streams): Renamed the restart around reads from + the user-input stream from ABORT to ABORT-READ. Invoking this + restart seems kinda dangerous, so better for 'a' in SLDB not to do + so. + +2004-06-28 Thomas F. Burdick <tfb(a)OCF.Berkeley.EDU> + + * swank.lisp (inspector-nth-part): + * slime.el (slime-inspector-copy-down, slime-inspector-mode-map): + Added copy-down command (M-RET) to easily move an object from the + inspector to the repl. + 2004-06-28 Luke Gorrie <luke(a)bluetail.com> * slime.el (slime-doc-map): New keymap for documentation

1 0

[slime-devel] New keybindings for documentation commands
by Luke Gorrie 29 Jun '04

29 Jun '04

Ahoy, As previously discussed the documentation commands have now been grouped under a `C-c C-d' prefix. The commands are: 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. The old bindings are removed. This has the nice effect that `C-c C-h' in a slime-mode buffer will now summarise the slime keybindings. It also shows that there are still two inf-lisp commands that we aren't currently clobbering, on `C-c C-a' and `C-c C-v'. Anyone want to fight over these bindings? I think we should have a bloody and decisive final keybinding war now and then make a 1.0-alpha release later this week. Cheers, Luke

4 5

[slime-devel] New keybindings for Who-xref commands
by Bill_Clementson＠peoplesoft.com 29 Jun '04

29 Jun '04

Attached is a patch that provides dual key bindings for the Who-xref commands (e.g. - it now allows either "C-c C-w c" or "C-c C-w C-c" for the "Who calls ..." command). This is in keeping with the Documentation key binding change. - Bill Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.345 diff -u -r1.345 slime.el --- slime.el 29 Jun 2004 17:39:01 -0000 1.345 +++ slime.el 29 Jun 2004 19:41:51 -0000 @@ -483,11 +483,6 @@ ("~" slime-sync-package-and-default-directory :prefixed t :inferior t) ("\M-p" slime-repl-set-package :prefixed t :inferior t) ;; Cross reference - ("\C-wc" slime-who-calls :prefixed t :inferior t :sldb t) - ("\C-wr" slime-who-references :prefixed t :inferior t :sldb t) - ("\C-wb" slime-who-binds :prefixed t :inferior t :sldb t) - ("\C-ws" slime-who-sets :prefixed t :inferior t :sldb t) - ("\C-wm" slime-who-macroexpands :prefixed t :inferior t :sldb t) ("<" slime-list-callers :prefixed t :inferior t :sldb t) (">" slime-list-callees :prefixed t :inferior t :sldb t) ;; "Other" @@ -516,6 +511,16 @@ (?h slime-hyperspec-lookup) (?~ common-lisp-hyperspec-format))) +(defvar slime-who-map (make-sparse-keymap) + "Keymap for who-xref commands. Bound to a prefix key.") + +(defvar slime-who-bindings + '((?c slime-who-calls) + (?r slime-who-references) + (?b slime-who-binds) + (?s slime-who-sets) + (?m slime-who-macroexpands))) + ;; Maybe a good idea, maybe not.. (defvar slime-prefix-key "\C-c" "The prefix key to use in SLIME keybinding sequences.") @@ -551,7 +556,17 @@ (let ((modified (slime-control-modified-char key))) (define-key slime-doc-map (string modified) command))))) ;; C-c C-d is the prefix for the doc map. - (slime-define-key "\C-d" slime-doc-map :prefixed t :inferior t)) + (slime-define-key "\C-d" slime-doc-map :prefixed t :inferior t) + ;; Who-xref + (setq slime-who-map (make-sparse-keymap)) + (loop for (key command) in slime-who-bindings + do (progn + ;; We bind both unmodified and with control. + (define-key slime-who-map (string key) command) + (let ((modified (slime-control-modified-char key))) + (define-key slime-who-map (string modified) command)))) + ;; C-c C-w is the prefix for the who-xref map. + (slime-define-key "\C-w" slime-who-map :prefixed t :inferior t)) (defun slime-control-modified-char (char) "Return the control-modified version of CHAR."

2 1

[slime-devel] Coding system oddities
by Lennart Staflin 29 Jun '04

29 Jun '04

Hello, I'm running slime on Mac OS X, with current (CVS) Emacs and openmcl. I tend to use Latin-1 coding for files, and the keyboard generates latin-1. In slime repl I get this (slightly edited for clairty): CL-USER> (print "Åhej") "\305hej" "Åhej" It seems that the coding system emacs uses for the printed output is another then used for the main slime interaction. Changing coding system for the output stream seems to confirm this: (set-process-coding-system (get-process "*lisp-output-stream*") 'latin-1 'latin-1) After that the above example gives: (print "Åhej") "Åhej" "Åhej" //Lennart Staflin

2 1

Re: [slime-devel] Re: New keybindings for documentation commands
by Bill_Clementson＠peoplesoft.com 29 Jun '04

29 Jun '04

Luke Gorrie <luke(a)bluetail.com> writes: > Peter Seibel <peter(a)javamonkey.com> writes: > > > Luke Gorrie <luke(a)bluetail.com> writes: > > > >> Ahoy, > >> > >> As previously discussed the documentation commands have now been > >> grouped under a `C-c C-d' prefix. The commands are: > >> > >> 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. > > > > Why? It seems silly to eat up twice as many key combos as we need to. > > (I haven't been following the discussion of this closely so if there > > was some reason that everyone already agreed was righteous you can > > just tell me so.) > > Well, at least I like the last key unmodified, and at least Bill > Clementson likes the last key modified. I figured that since they're > already on their own documentation-commands prefix (C-c C-d) that > we're unlikely to run out of keys, so we can just make everyone happy > in this respect. > > There's still meta if we do end up running out of letters. :-) We had a similar discussion on the ilisp-devel list last year when we were changing key bindings so that they conformed to fsf standards. Some people (including me at that time) liked the unmodified last key and some preferred a modified last key for key chords that had to use 3 keys. Andreas Fuchs summed up his rationale for the modified key option in this posting: http://sourceforge.net/mailarchive/forum.php?thread_id=2389721&forum_id=5779 A few other people agreed with Andreas - I tried out both combinations and came around to Andreas' POV as well. However, some people (Luke included) prefer the other approach. Remember, this is only an issue with the 3-key chords as the 2-key chords need to be bound to either a control key (for each key) or a special character (for the second key) in order to conform to fsf major mode standards. Since we only use 3-key chords for certain "groups" of commands (e.g. -- documentation), we are probably not going to run out of 3-key sequences any time soon ;-) So, it probably doesn't hurt to bind to both sets of keys as it will keep everybody happy :-) - Bill

1 0

[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