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

[slime-devel] slime apparently mis-reporting closed connection
by Samium Gromoff 26 Oct '07

26 Oct '07

After well into the second decade of slime-disconnect/slime-connect loop iteration (interweaved with normal operation) the emacs side of slime stopped recognising connection status. I`m doing a slime-disconnect, restarting swank and slime-connect, however immediately after this either a slime-load-file or a (load ...) in slime repl result in a message "Connection closed." i have some time before i will have to reboot the machine, and until then i can provide various forensics upon request... regards, Samium Gromoff

5 5

[slime-devel] slime-apropos-package now sorts correctly
by Hoehle, Joerg-Cyril 20 Apr '07

20 Apr '07

Hi, slime-apropos-package now conforms to its specification and also sorts symbols printed with package prefix. I supply the patches as attachments in the hope that MS-Windows nor MS-Outlook will break the TAB and LF characters of the original diff. I hope this is fine. Regards, Jörg Höhle.

3 3

[slime-devel] slime-display-edit-hilights
by Marco Baringer 23 Dec '06

23 Dec '06

for those of you who don't follow c.l.l (which is probaly a good idea) i commited William Bland's patch[1]. see the ChangeLog for details. 1 - http://groups.google.com/group/comp.lang.lisp/browse_thread/thread/e1d0b7bf… -- -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

8 20

[slime-devel] How to inspect locals
by Jonathon McKitrick 27 Aug '06

27 Aug '06

Hi all, when running SBCL and a condition occurs that causes a break, how can I view the locals that have been bound in the function? Viewing the arguments isn't hard, but I cannot seem to figure out the locals. -Jonathon -- "I am sure that Jesus would use a command prompt. Hello? Ten Commandments??"

12 17

[slime-devel] swank reloading problem
by Cyrus Harmon 19 Jun '06

19 Jun '06

I'm trying to debug getting threads running on SBCL/x86/MacOS and in doing so I've come across a strange problem where something (presumably clim-desktop.asd) is requiring swank, which is causing swank.asd to get reloaded and swank-backend is getting recompiled, which causes current-thread to get redefined to 0. This seems to wreak havoc with some of the locking stuff, which presumably has various locks held while it's trying to output the results of the compilation. Should the definterface stuff in swank-backend have some sort of check to see if these haven't been previously implemented before overwriting the previous method definitions? Thanks, Cyrus

4 4

[slime-devel] Fuzzy completion
by Levente Mészáros 16 Jun '06

16 Jun '06

Hi, Although I'm not a big emacs guru, so things might be implemented simpler, but I did what I could with a resonable effort. Still you may or may not find this useful. This is not a final patch for two reasons: first I'm not even sure it's worth it and if nobody is interested I will just keep it in my local repo. Second, it breaks current functionality: the one which continuously replaces text in the target buffer while you move up and down in the completion window with the current completion (selection). Personally I found that superfluous. So this is a somewhat different end user experience for fuzzy completion. It is a little bit closer to the other non fuzzy completion in that it does not take the focus away from the buffer you are editing and there are some other minor differences. I introduced a new minor mode called slime-fuzzy-target-buffer-completions-mode for the target buffer during fuzzy completion. You may find it usefull to bind your paredit open and close keys to (the ones bound to insert-parentheses and move-past-close-and-reindent) slime-fuzzy-select-and-process-event-in-target-buffer in the keymaps called slime-target-buffer-fuzzy-completions-map and slime-fuzzy-completions-map. Here is how it works (- means not yet implemented): When focus is in the target window (replace tab with your favorite key binding): + tab shows completion window if it was not open + tab updates completion window if there was editing since last time tab was pressed + tab implicitly completes if there's only one match + tab selects current completion if there were no editing since last tab (double tab) even if there are multiple matches + tab closes completion window if there are no matches at all - tab distinguishes between function and other symbols and puts an extra space before caret if mandatory parameters exists - tab puts the caret after the list in the target for unary function symbols + left/right moves caret in target window + up/down moves caret in completion window even though the focus is in the target window (changes current completion) + space/enter/(/) implicitly selects current completion and processes event in target window (paredit takes care about the rest) + normal editing operations allowed in target window - editing implicitly updates completion window in the background during editing (by a timer) + C-q closes completion window When focus is in the completion window: + cursor keys navigate + tab/mouse2 selects current completion and closes completion window + space/enter/(/) selects current completion, closes completion window and processes event in the target window + q closes completion window Cheers, levy -- There's no perfectoin

5 4

[slime-devel] Slime/CMU hangs on GC
by Florian Ebeling 05 Jun '06

05 Jun '06

My emacs in slime mode hangs quite oft imidiatly after announcing a GC run, usually from a Slime mode buffer, not from REPL. I use CMUCL and Slime from CVS. Is this a known behaviour? Florian -- Florian Ebeling florian.ebeling(a)gmail.com

4 3

[slime-devel] On the numbering of restarts in SLDB
by Gary King 31 May '06

31 May '06

Although it makes perfect sense, I find it irritating that the number for the [abort-request] restart in SLDB depends on how many other restarts are active. For clarity's sake, here is a list of restarts: > Restarts: > 0: [RETRY] Retry performing #<LOAD-OP NIL #x84F81F6> on #<SYSTEM > "cl-containers" #x84E8EE6>. > 1: [ACCEPT] Continue, treating #<LOAD-OP NIL #x84F81F6> on > #<SYSTEM "cl-containers" #x84E8EE6> as having been successful. > 2: [ABORT-REQUEST] Abort handling SLIME request. > 3: [ABORT-BREAK] Reset this process > 4: [ABORT] Kill this process In this case, I should type '2' to give up on this request and try something else. In other cases, however, I might need to type '7' or '5' or whatever. This means that I have to look and see what to type every single time I hit an error (and, hey, I hit a lot of errors in my code!). It also scares me that I could misread and type the key for [abort-break] or [abort] by accident. Here is my suggestion as to what the list of restarts might look like: > Restarts: > 4: [RETRY] Retry performing #<LOAD-OP NIL #x84F81F6> on #<SYSTEM > "cl-containers" #x84E8EE6>. > 3: [ACCEPT] Continue, treating #<LOAD-OP NIL #x84F81F6> on > #<SYSTEM "cl-containers" #x84E8EE6> as having been successful. > 2: [ABORT-REQUEST] Abort handling SLIME request. > 1: [ABORT-BREAK] Reset this process > 0: [ABORT] Kill this process or > Restarts: > 0: [RETRY] Retry performing #<LOAD-OP NIL #x84F81F6> on #<SYSTEM > "cl-containers" #x84E8EE6>. > 1: [ACCEPT] Continue, treating #<LOAD-OP NIL #x84F81F6> on > #<SYSTEM "cl-containers" #x84E8EE6> as having been successful. > A: [ABORT-REQUEST] Abort handling SLIME request. > R: [ABORT-BREAK] Reset this process > K: [ABORT] Kill this process In both cases, the three 'always there' restarts will always have the same keyboard binding. In the later example, they are non-numeric. I'm willing to figure out how to implement this _if_ the general opinion is that this is a good idea. What is the general opinion? thanks, -- Gary Warren King metabang.com http://www.metabang.com/ (413) 210 7511 gwking on #lisp (occasionally)

8 9

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 30 May '06

30 May '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.901 slime/ChangeLog:1.903 --- slime/ChangeLog:1.901 Sat May 27 05:06:12 2006 +++ slime/ChangeLog Mon May 29 19:41:00 2006 @@ -1,3 +1,30 @@ +2006-05-30 Tobias Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-get-temp-buffer-create): New keyword REUSEP + which indicates whether an already-existing buffer named like the + buffer to be created should be reused, i.e. not killed, then + freshly created. Update docstring accordingly. + (slime-with-output-to-temp-buffer): Make &optional arg MODE an + &key keyword arg. Add REUSEP keyword. + (slime-macroexpansion-minor-mode-map): Make remapped `undo' update + highlighted edits in the macroexpansion buffer. + (slime-eval-macroexpand-in-place): Update highlighted edits when + macroexpanding in-place. + (slime-eval-macroexpand): Reuse macroexpansion buffer if it exists + already to preserve `undo' functionality. + +2006-05-30 Tobias Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-use-autodoc-mode): Fix typo in docstring. + (slime-use-highlight-edits-mode): New variable, analogous to + SLIME-USE-AUTODOC-MODE. + (slime-setup, slime-lisp-mode-hook): Make above variable + work. Also, activates the HIGHLIGHT-EDITS-MODE in proper way (thus + avoiding the nasty "Toggling ... off; better pass an explicit + argument." message.) + + * slime.el: Fix typo in comment about communication protocol. + 2006-05-27 Alan Ruttenberg <alanr-l(a)mumble.net> * swank-abcl: slot-boundp-using-class slot-value-using-class so you can inspect instances

1 0

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 28 May '06

28 May '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.900 slime/ChangeLog:1.901 --- slime/ChangeLog:1.900 Sat May 27 00:18:13 2006 +++ slime/ChangeLog Sat May 27 05:06:12 2006 @@ -11,7 +11,7 @@ Also make expanding of expressions work that are quoted like, for instance, "'(FOO BAR)" if point is placed at the opening paren. -006-05-24 Brian Downing <bdowning(a)lavos.net> +2006-05-24 Brian Downing <bdowning(a)lavos.net> * swank.lisp (recursively-compute-most-completions & friends): Micro-optimize the fuzzy completion engine, improving performace

1 0

[slime-devel] [Patch] making REPL buffer paredit-friendly
by Ivan Shvedunov 27 May '06

27 May '06

Hi. As of now, when paredit is used for REPL buffer, history doesn't work because closing parentheses are inserted automatically. E.g. I type (| at the point): (format|) and press M-p, but nothing is found because the whole input is used. I think the reasonable way to fix this is to use the portion of input between slime-repl-input-start-mark and (point) for history search. The attached trivial patch does just that. I hope such behavior will not interfere with anyone's habits as when paredit is not used M-p is usually pressed when the point is at the end of input. When the point is at slime-repl-input-mark or before it, the old behavior is used. Ivan

1 0

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 27 May '06

27 May '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.898 slime/ChangeLog:1.900 --- slime/ChangeLog:1.898 Wed May 24 23:15:20 2006 +++ slime/ChangeLog Sat May 27 00:18:13 2006 @@ -1,4 +1,17 @@ -2006-05-24 Brian Downing <bdowning(a)lavos.net> +2006-05-27 Alan Ruttenberg <alanr-l(a)mumble.net> + * swank-abcl: slot-boundp-using-class slot-value-using-class so you + can inspect instances + +2006-05-26 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-eval-macroexpand-inplace): Fix out-of-range + error on in-place macroexpand when point is placed at a closing + parenthesis. In this case the sexp closed by that paren is + expanded. + Also make expanding of expressions work that are quoted like, for + instance, "'(FOO BAR)" if point is placed at the opening paren. + +006-05-24 Brian Downing <bdowning(a)lavos.net> * swank.lisp (recursively-compute-most-completions & friends): Micro-optimize the fuzzy completion engine, improving performace

2 1

[slime-devel] [Patch] Fix for out-of-range error when macroexpanding in-place
by Tobias C. Rittweiler 26 May '06

26 May '06

2006-06-26 Tobias C. Rittweiler <PUT-MY-ADDRESS-HERE> * slime.el (slime-eval-macroexpand-inplace): Fix out-of-range error on in-place macroexpand when point is placed at a closing parenthesis. In this case the sexp closed by that paren is expanded. Also make expanding of expressions work that are quoted like, for instance, "'(FOO BAR)" if point is placed at the opening paren. --- slime.el-old 2006-05-26 19:44:07.000000000 +0200 +++ slime.el 2006-05-26 21:42:31.000000000 +0200 @@ -7378,10 +7378,17 @@ NB: Does not affect *slime-eval-macroexpand-expression*" (interactive) (lexical-let* ((string (slime-sexp-at-point-or-error)) + (bounds (bounds-of-thing-at-point 'sexp)) + (start (car bounds)) + (end (cdr bounds)) + (point (point)) (package (slime-current-package)) - (start (point)) - (end (+ start (length string))) (buffer (current-buffer))) + ;; SLIME-SEXP-AT-POINT returns "'(FOO BAR BAZ)" even when point is + ;; placed at the opening parenthesis, which wouldn't get expanded + ;; even though FOO was a macro. Hence this workaround: + (when (and (eq ?\' (elt string 0)) (eq ?\( (elt string 1))) + (setf string (substring string 1)) (incf start) (slime-eval-async `(,expander ,string) (lambda (expansion) @@ -7393,7 +7400,8 @@ (delete-region start end) (insert expansion) (goto-char start) - (indent-sexp))))))) + (indent-sexp) + (goto-char point))))))) (defun slime-macroexpand-1 (&optional repeatedly) "Display the macro expansion of the form at point. The form is

1 1

[slime-devel] slime-edit-definition problem
by Gábor Melis 25 May '06

25 May '06

I am running debian/etch with emacs21.4a-3. Some time ago - maybe when emacs was upgraded - M-. stopped working. Well, it works if there are multiple choices, but if there is just one, then it prints the error: Args out of range: #^[t nil 0 1 2 3 4 5 6 7 ... ], -134217682 It seems that find-file-noselect is the culprit, but I have no idea what's wrong with it. The strange thing is that if I define another mapping for slime-edit-definition then that works where the other doesn't: (define-key slime-repl-mode-map "\C-ci" 'slime-edit-definition) It's the same under both sbcl and allegro. Cheers, Gábor

2 3

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 25 May '06

25 May '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.896 slime/ChangeLog:1.898 --- slime/ChangeLog:1.896 Tue May 16 14:04:49 2006 +++ slime/ChangeLog Wed May 24 23:15:20 2006 @@ -1,3 +1,17 @@ +2006-05-24 Brian Downing <bdowning(a)lavos.net> + + * swank.lisp (recursively-compute-most-completions & friends): + Micro-optimize the fuzzy completion engine, improving performace + by a factor of about 4 on SBCL. However, it will only work on + simple-strings now, and CHAR= is burned in instead of being an + option. I don't think this is too much of a limitation. At this + point rendering the results on the emacs side takes much longer + than finding them for long result lists. + +2006-05-24 Alan Ruttenberg <alanr-l(a)mumble.net> + * swank-abcl: Add some more mop functions to you can inspect classes, + generic functions, methods, slots. + 2006-05-16 Marco Baringer <mb(a)bese.it> * slime.el (slime-repl-return-behaviour): New variable which

1 0

[slime-devel] slime-fuzzy-complete-symbol
by Levente Mészáros 25 May '06

25 May '06

Hi, I'm wondering how others use slime-fuzzy-complete-symbol? Do you use it at all? Do you use it with the default user interface or do you have customized it? I think it's great but the user interface could be tuned a little bit. (at least to my taste) Here is my idea (which I might eventually implement): - in the source window use <TAB> key to show the fuzzy completion list - simultanously in the match window display the possible matches and highlight the first one as being the current fuzzy completion - do not change anything in the source window and let the focus stay there (this is different from the one currently implemented) - use the subsequent <TAB> keypresses to iterate through the possible matches and use S-<TAB> to go backwards. one can always switch to the completion list window and navigate back and forth with the usual keystrokes if one wants to - otherwise the focus stays in the source window and no changes there - if you hit any key that clearly stops editing the current symbol in the source window, then the incomplete symbol will be replaced by the current fuzzy match and the key will be evaluated afterwards (implicit completion). such keys are space, enter, (), arrow keys leaving the symbol, etc... of course, hide completion window - if you did not find a match or there are too many matches, you can continue editing by navigating back, deleting back, etc. - the completion window remains there and continuously updates making the first match as the current completion, so that you can hit space, enter, () to commit to type in slot-value-using-class one would type: ( svuc TAB SPACE object SPACE slot ) levy -- There's no perfectoin

3 6

[slime-devel] REPL-specific printer control variables
by Robert J. Macomber 24 May '06

24 May '06

This patch adds two variables to swank: *listener-print-level* and *listener-print-length*, analogous to the standard Lisp variables *print-level* and *print-length*, used to control how much of a form's return values get printed at the REPL but not of things printed directly by user code. If they're bound (by default, they aren't) then swank uses them when preparing the presentation of an evaluation's result for sending to Emacs. When they're unbound, the values of the standard CL depth and length variables instead. I've written this because of one too many "oops, I forgot to wrap that form in a (progn ... nil)" mistakes on my part. Not a fatal error, but it can be inconvenient. -- Robert Macomber slime(a)rojoma.com

2 3

[slime-devel] significance of *error-output*/*standard-output* in the REPL
by David A Thompson 19 May '06

19 May '06

I suspect this question/issue is already addressed in SLIME documentation (where?) or has been touched on in a mailing list before but... Google and a search of the archives via gmane have let me down so... apologies up front. In short, how does one suppress compiler error warnings in the SLIME REPL (I'm using SLIME with SBCL)? This issue arose in the context of a program which generates thousands of compiler error conditions (intentionally) as it evaluates a large collection of sexps. (As one might imagine), execution is slowed down substantially by the verbosity that accompanies these error messages when each message much be sent to the terminal. Even with a handler in place, SBCL still likes to let everyone know a compiler error has occurred so I end up with thousands of lines in the REPL along the lines of: ; in: LAMBDA NIL ; ((KNOT) ((D1))) ; ; caught ERROR: ; illegal function call Setting *error-output* or *standard-output* to (make-broadcast-stream) is the minimal-effort fix under SBCL if it is used in a regular terminal (e.g., xterm) but, in the context of SLIME, these settings seem to be ignored. SLIME seems to globally redirect streams to the REPL (as the SLIME manual suggests) regardless of *error-output* and/or *standard-output* settings. Is there any way to override this behavior and suppress/divert such error messages? (something related to swank::*globally-redirect-io*?) Thanks for your good graces and any suggestions, - Alan

4 3

[slime-devel] Highlight edits mode
by Levente Mészáros 18 May '06

18 May '06

Is there a way to use highlight edits mode with require? Often I edit several files in several places and then require some system. I would expect resetting highlights in files loaded by require. I know C-c C-c and friends remove highlights but require does not. Probably it's difficult to communicate the loaded files to emacs... How do you use this feature? Cheers, levy -- There's no perfectoin

1 0

[slime-devel] [Patch] improving interaction of macroexpansion and highlighting edits.
by Tobias C. Rittweiler 18 May '06

18 May '06

The attached patch improves the interaction between SLIME-HIGHLIGHT-EDITS-MODE and SLIME-MACROEXPANSION-MINOR-MODE such that macroexpanding in-place will highlight the affected region only. Same happens when going-back to the previous macroexpansion by `undo'. It depends on my last patch which introduces the global variable SLIME-USE-HIGHLIGH-EDITS-MODE. One issue remains: As of now, it's possible to get to an empty Macroexpansion Buffer by `undo'. I have a local hack that all it basically does, is (remap 'undo (lambda (arg) ... (undo arg) (when (zerop (buffer-size)) (redo)))) Though, as you see, that makes use of redo.el which is not part of standard Emacs, unfortunately. 2006-05-18 Tobias C. Rittweiler <PUT-MY-ADDRESS-HERE> * slime.el (slime-get-temp-buffer-create): New keyword REUSEP which indicates whether an already-existing buffer named like the buffer to be created should be reused, i.e. not killed, then freshly created. Update docstring accordingly. (slime-with-output-to-temp-buffer): Make &optional arg MODE an &key keyword arg. Add REUSEP keyword. * slime.el (slime-macroexpansion-minor-mode-map): Make remapped `undo' update highlighted edits in the macroexpansion buffer. (slime-eval-macroexpand-in-place): Update highlighted edits when macroexpanding in-place. (slime-eval-macroexpand): Reuse macroexpansion buffer if it exists already to preserve `undo' functionality. --- /home/tcr/src/from-upstream/slime/slime.el 2006-05-18 16:25:50.000000000 +0200 +++ slime.el 2006-05-18 16:34:01.000000000 +0200 @@ -1186,16 +1190,19 @@ "The window config \"fingerprint\" after displaying the buffer.")) ;; Interface -(defun* slime-get-temp-buffer-create (name &key mode noselectp) +(defun* slime-get-temp-buffer-create (name &key mode noselectp reusep) "Return a fresh temporary buffer called NAME in MODE. The buffer also uses the minor-mode `slime-temp-buffer-mode'. Pressing `q' in the buffer will restore the window configuration to the way it is when the buffer was created, i.e. when this function was called. -If NOSELECTP is true then the buffer is shown by `display-buffer', -otherwise it is shown and selected by `pop-to-buffer'." +If NOSELECTP is true, then the buffer is shown by `display-buffer', +otherwise it is shown and selected by `pop-to-buffer'. + +If REUSEP is true and a buffer does already exist with name NAME, +then the buffer will be reused instead of being killed." (let ((window-config (current-window-configuration))) - (when (get-buffer name) (kill-buffer name)) + (when (and (get-buffer name) (not reusep)) (kill-buffer name)) (with-current-buffer (get-buffer-create name) (when mode (funcall mode)) (slime-temp-buffer-mode 1) @@ -1208,14 +1215,17 @@ (current-buffer)))) ;; Interface -(defmacro* slime-with-output-to-temp-buffer ((name &optional mode) +(defmacro* slime-with-output-to-temp-buffer ((name &key mode reusep) package &rest body) "Similar to `with-output-to-temp-buffer'. Also saves the window configuration, and inherits the current `slime-connection' in a buffer-local variable." `(let ((connection (slime-connection)) - (standard-output (slime-get-temp-buffer-create ,name :mode ',mode))) - (prog1 (with-current-buffer standard-output ,@body) + (standard-output (slime-get-temp-buffer-create ,name :mode ',mode + :reusep ,reusep))) + (prog1 (with-current-buffer standard-output + ;; set explicitely to NIL in case the buffer got reused. (REUSEP) + (let ((buffer-read-only nil)) ,@body)) (with-current-buffer standard-output (setq slime-buffer-connection connection) (setq slime-buffer-package ,package) @@ -7018,7 +7028,7 @@ (defun slime-show-apropos (plists string package summary) (if (null plists) (message "No apropos matches for %S" string) - (slime-with-output-to-temp-buffer ("*SLIME Apropos*" apropos-mode) package + (slime-with-output-to-temp-buffer ("*SLIME Apropos*" :mode apropos-mode) package (set-syntax-table lisp-mode-syntax-table) (slime-mode t) (if (boundp 'header-line-format) @@ -7338,6 +7348,8 @@ (remap 'undo '(lambda (&optional arg) (interactive) (let ((buffer-read-only nil)) + (when slime-use-highlight-edits-mode + (slime-remove-edits (point-min) (point-max))) (undo arg))))) (defvar slime-eval-macroexpand-expression nil @@ -7353,8 +7365,10 @@ slime-eval-macroexpand-expression (lambda (expansion) (slime-with-output-to-temp-buffer - ("*SLIME macroexpansion*" lisp-mode) package + ;; reusep for preserving `undo' functionality. + ("*SLIME macroexpansion*" :mode lisp-mode :reusep t) package (slime-macroexpansion-minor-mode) + (erase-buffer) (insert expansion) (font-lock-fontify-buffer)))))) @@ -7373,6 +7387,8 @@ (lambda (expansion) (with-current-buffer buffer (let ((buffer-read-only nil)) + (when slime-use-highlight-edits-mode + (slime-remove-edits (point-min) (point-max))) (goto-char start) (delete-region start end) (insert expansion)

1 0

[slime-devel] [Patch] setting up highlight-edits-mode in a proper way
by Tobias C. Rittweiler 18 May '06

18 May '06

2006-05-18 Tobias Rittweiler <PUT-MY-ADDRESS-HERE> * slime.el (slime-use-autodoc-mode): Fix typo in docstring. * slime.el (slime-use-highlight-edits-mode): New variable, analogous to SLIME-USE-AUTODOC-MODE. (slime-setup, slime-lisp-mode-hook): Make above variable work. Also, activates the HIGHLIGHT-EDITS-MODE in proper way (thus avoiding the nasty "Toggling ... off; better pass an explicit argument." message.) * slime.el: Fix typo in comment about communication protocol. --- /home/tcr/src/from-upstream/slime/slime.el 2006-04-15 15:46:14.000000000 +0200 +++ slime.el 2006-05-11 18:09:30.000000000 +0200 @@ -65,7 +65,10 @@ (require 'easymenu) (defvar slime-use-autodoc-mode nil - "When non-nil always enabled slime-autodoc-mode in slime-mode.") + "When non-nil always enable slime-autodoc-mode in slime-mode.") + +(defvar slime-use-highlight-edits-mode nil + "When non-nil always enable slime-highlight-edits-mode in slime-mode") (defun* slime-setup (&key autodoc typeout-frame highlight-edits) "Setup Emacs so that lisp-mode buffers always use SLIME." @@ -73,15 +76,16 @@ (when typeout-frame (add-hook 'slime-connected-hook 'slime-ensure-typeout-frame)) (setq slime-use-autodoc-mode autodoc) - (when highlight-edits - (add-hook 'slime-mode-hook 'slime-highlight-edits-mode))) + (setq slime-use-highlight-edits-mode highlight-edits)) (defun slime-lisp-mode-hook () (slime-mode 1) (set (make-local-variable 'lisp-indent-function) 'common-lisp-indent-function) (when slime-use-autodoc-mode - (slime-autodoc-mode 1))) + (slime-autodoc-mode 1)) + (when slime-use-highlight-edits-mode + (slime-highlight-edits-mode 1))) (eval-and-compile (defvar slime-path @@ -2281,8 +2294,8 @@ This is set only in buffers bound to specific packages.")) ;;; `slime-rex' is the RPC primitive which is used to implement both -;;; `slime-eval' and `slime-eval-async'. You can use it directly you -;;; need to but the others are usually more convenient. +;;; `slime-eval' and `slime-eval-async'. You can use it directly if +;;; you need to, but the others are usually more convenient. (defmacro* slime-rex ((&rest saved-vars) (sexp &optional

1 0

[slime-devel] Search definition
by Levente Mészáros 18 May '06

18 May '06

Hi, I wrote a slime extension to search definitions (variables,.functions, generic functions, etc.) based on fuzzy completions and edit definiton. It's supposed to work like apropos, but the result is interactive. Here is the idea (although not yet fully implemented) + hitting search definitons key brings up minibuffer + while editing in the minibuffer you can press TAB which shows fuzzy competion list for the current content of the minibuffer + completion list has a current selection + up/down arrows move the current selection while leaving the focus in the minibuffer, so that you can edit and hit TAB again to update the completion window + hitting enter goes to the definiton in the source files currently selected and closes minibuffer and completion window and leaves the source buffer open + hitting space opens the definition while leaving the focus in the minibuffer (minibuffer, completion window and definition window is visible at the same time) + hitting space on several definitons will show the sources of the definitons on top of each other + ESC leaves search definition - completion window shows specialized versions of generic functions in place, so that it can be selected directly (tree) - switch between two modes, where changing the selection immediately shows the definition of the current selection, so you can just move up and down (C-SPACE?) - close all sources that were not open before starting find definition except the one that was opened by pressing enter Key bindings are local to search definitions. Any ides, suggestions? levy -- There's no perfectoin

2 1

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 17 May '06

17 May '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.895 slime/ChangeLog:1.896 --- slime/ChangeLog:1.895 Sun May 14 09:25:01 2006 +++ slime/ChangeLog Tue May 16 14:04:49 2006 @@ -1,3 +1,9 @@ +2006-05-16 Marco Baringer <mb(a)bese.it> + + * slime.el (slime-repl-return-behaviour): New variable which + controls slime-repl-return's heaviour. + (slime-repl-return): Respect slime-repl-return-behaviour. + 2006-05-14 Marco Baringer <mb(a)bese.it> * slime.el (slime-macroexpansion-minor-mode-map): Rebind 'undo' to

1 0

[slime-devel] How to erase input lines in REPL?
by doug arro 17 May '06

17 May '06

My configuration is slime 2.0 + sbcl 0.9.12. When I enter something like this at the REPL prompt: CL-USER>line1 to be erased line 2 to be erased How do I erase the lines without using the backspace key and get back to the REPL prompt? Doug --------------------------------- Blab-away for as little as 1¢/min. Make PC-to-Phone Calls using Yahoo! Messenger with Voice.

7 12

[slime-devel] XREF failure on ACL 7.0
by Julian Stecklina 15 May '06

15 May '06

Hello, using stuff like C-c C-w resulted in an error with Allegro CL 7.0 because in fspec-definition-locations in swank-allegro.lisp the destructuring-bind was given a list without position element. A quick fix is: Index: swank-allegro.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-allegro.lisp,v retrieving revision 1.87 diff -u -r1.87 swank-allegro.lisp --- swank-allegro.lisp 4 May 2006 14:38:07 -0000 1.87 +++ swank-allegro.lisp 15 May 2006 20:39:32 -0000 @@ -402,8 +402,10 @@ (defun fspec-definition-locations (fspec) (cond ((and (listp fspec) - (eql (car fspec) :top-level-form)) - (destructuring-bind (top-level-form file position) fspec + (eql (car fspec) :top-level-form) + (= (length fspec) 3)) + (destructuring-bind (top-level-form file position) fspec + (declare (ignore top-level-form)) (list (list (list nil fspec) (make-location (list :buffer file) Regards, -- Julian Stecklina "I object to doing things that computers can do." - Olin Shivers

1 0