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

[slime-devel] SLIME via ssh?
by Nicolas Neuss 14 Apr '05

14 Apr '05

Hello, I have SBCL running on an Opteron Cluster (at the moment only one process). This cluster has no Emacs installed. I can connect to it only with ssh. 1. Is it possible to control the remote SBCL job with SLIME running on my own computer (a Laptop)? Can SLIME work also with remote files via Tramp (e.g. by sending expressions to the remote SBCL)? How is the setup? 2. It would be nice if the SBCL job could be kept running (doing a lengthy calculation) while I disconnect and log out (e.g. when carrying my Laptop to another place). What is the right thing to do here? Maybe screen or detachtty? Both are not installed yet, but this would probably be easy... Thanks for any hints, Nicolas.

4 5

[slime-devel] suggested macroexpansion feature (and volunteer)
by Chris Capel 13 Apr '05

13 Apr '05

I've been thinking about a neat feature I think could be implemented in a pretty straightforward way to help with the debugging of macros. There would be a new minor mode for a buffer containing some random form. Selecting any given subform of the buffer's form would macroexpand that one form, in place. Of course, it would have to respect macrolet's and symbol-macrolet's (which isn't that hard, really). I already have the code written (included below) to expand such forms (perhaps buggy, perhaps incomplete). (One thing I know it doesn't do is find and respect macrolets that aren't present in the form until after some expansion. I don't know that this is a big deal.) What's missing is the hooks into slime and Emacs. I don't want to bother with these (because they'd be a lot more effort for me) until I find whether there are any similar features currently available for SLIME. So has anyone done anything like this yet? If not, I suppose SLIME would need another minor mode with some cool keybindings and code to figure out what to pass as the list-indexes variable based on the position in the buffer (perhaps the hardest part?). Chris Capel (defmacro expand (form &environment e) (list 'quote (macroexpand-1 form e))) (defun get-list-to-expand (list list-indexes) (flet ((recurse () (get-list-to-expand (nth (car list-indexes) list) (cdr list-indexes)))) (if (null list-indexes) (list 'expand list) (let ((sym (find (car list) '(macrolet symbol-macrolet)))) (if sym (list sym (cadr list) (recurse)) (recurse)))))) (get-list-to-expand '(symbol-macrolet ((s a)) s) '(2)) (defun nsubst-list (source substitution list-indexes) (if (null list-indexes) substitution (progn (setf (nth (car list-indexes) source) (nsubst-list (nth (car list-indexes) source) substitution (cdr list-indexes))) source))) (nsubst-list '(a b (c d)) '(e f) '(2 1)) (defun subst-all-tree (tree obj-a obj-b &key (test #'equal)) (mapcar (lambda (i) (if (consp i) (subst-all-tree i obj-a obj-b :test test) (if (funcall test obj-a i) obj-b i))) tree)) (subst-all-tree '(a b (c d)) 'd 'e) (defun expand-part (list &rest list-indexes) (nsubst-list list (eval (get-list-to-expand list list-indexes)) list-indexes)) (expand-part '(macrolet ((x (m) `(y ,m))) (x z)) 2) (expand-part '(let ((x 50)) (destructuring-bind (x y z) f (dolist (q y) x))) 2) ;; or "2 3)" for the dolist

2 2

Re: [slime-devel] Re: Question about useage
by Jeffrey Cunningham 10 Apr '05

10 Apr '05

Thanks! -jeff

1 0

[slime-devel] Question about useage
by Jeffrey Cunningham 10 Apr '05

10 Apr '05

This is probably a dumb question, but I haven't been able to figure it out yet. If I'm working with Slime and have defined some method functions for CLOS objects and want to change the number of arguments, when I go to compile one it objects with something like: "Attempt to add the method #<Standard-Method LIST-PARMS (TRACK-CLASS) {48BAC95D}> to the generic function #<Standard-Generic-Function LIST-PARMS (6) {484A09A1}>." I knew that. I was trying to change them all. Is there a way to clear the existence of these functions from lisp's "memory" and start over? Or do I have to kill the session and start it up again? Thanks. --Jeff

3 2

[slime-devel] Problem with SBCL, Slime, and infix.lisp (gack!)
by Brian Downing 10 Apr '05

10 Apr '05

I think this is an SBCL problem (as it doesn't happen in CMUCL), but Slime code tickles it so I'm sending it to both lists. With SBCL, Slime can't find it's way past an infix expression with source-path-stream-position. Because of this, when compiling files with C-c C-k, any notes, warnings, or errors will cause an unrelated infix error. To test this you'll obviously need to load infix.cl, available from http://www.cs.cmu.edu/afs/cs/project/ai-repository/ai/lang/lisp/code/syntax… Put a file somewhere containing these two lines: (quote #i( 2 )) (quote nothing) With Swank loaded, in CMUCL: CL-USER> (with-open-file (f "/tmp/test.lisp") (swank-backend::source-path-stream-position '(1 0) f)) 17 22 With SBCL (0.8.21.26, x86/Linux): CL-USER> (with-open-file (f "/tmp/test.lisp") (swank-backend::source-path-stream-position '(1 0) f)) Infix expression ends with NIL. [Condition of type SIMPLE-ERROR] Restarts: 0: [ABORT] Abort handling SLIME request. 1: [ABORT] Exit debugger, returning to top level. Backtrace: 0: (INFIX::READ-INFIX #<SB-SYS:FD-STREAM for "file \"/tmp/test.lisp\"" {9CB17A1}>) 1: (INFIX::INFIX-READER #<SB-SYS:FD-STREAM for "file \"/tmp/test.lisp\"" {9CB17A1}> #<unavailable argument> #<unavailable argument>) 2: (SB-IMPL::READ-MAYBE-NOTHING #<SB-SYS:FD-STREAM for "file \"/tmp/test.lisp\"" {9CB17A1}> #\#) 3: (SB-IMPL::READ-LIST #<SB-SYS:FD-STREAM for "file \"/tmp/test.lisp\"" {9CB17A1}> #<unavailable argument>) 4: (READ-PRESERVING-WHITESPACE #<SB-SYS:FD-STREAM for "file \"/tmp/test.lisp\"" {9CB17A1}> T NIL T) 5: (READ-PRESERVING-WHITESPACE #<SB-SYS:FD-STREAM for "file \"/tmp/test.lisp\"" {9CB17A1}> T NIL NIL) 6: (READ #<SB-SYS:FD-STREAM for "file \"/tmp/test.lisp\"" {9CB17A1}> T NIL NIL) 7: (SWANK-BACKEND::READ-SOURCE-FORM 1 #<SB-SYS:FD-STREAM for "file \"/tmp/test.lisp\"" {9CB17A1}>) 8: (SWANK-BACKEND::SOURCE-PATH-STREAM-POSITION (1 0) #<SB-SYS:FD-STREAM for "file \"/tmp/test.lisp\"" {9CB17A1}>) This problem is absolutely NOT critical to me, it just came up while trying to help someone on c.l.l. -bcd

1 1

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 09 Apr '05

09 Apr '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.662 slime/ChangeLog:1.663 --- slime/ChangeLog:1.662 Thu Apr 7 12:00:40 2005 +++ slime/ChangeLog Sat Apr 9 09:08:21 2005 @@ -1,3 +1,25 @@ +2005-04-09 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (sldb-get-buffer): Create a fresh buffer if there's no + buffer for the connection (and don't reuse an existing buffer even + if it has a matching name). + (slime-buffer-visible-p, slime-ir1-expand): Delete unused + functions. Mark some others as unused, but leave them there + because they are potentially useful. + + * swank.lisp (with-io-redirection, with-connection) + (with-buffer-syntax): Implement macros with a `call-with' + functions to avoid some code bloat. + (call-with-connection, maybe-call-with-io-redirection) + (call-with-buffer-syntax): New functions. + (interactive-eval): Use from-string instead of read-from-string to + avoid problems whit *read-suppress*. + + * swank-sbcl.lisp: Add a few comments. + + * swank-abcl.lisp (print-frame): Trim whitespace to make the + backtrace look a bit terser. + 2005-04-07 Helmut Eller <heller(a)common-lisp.net> * slime.el (slime-net-coding-system): More fixes for

1 0

[slime-devel] Re: [slime-cvs] CVS update: slime/doc/slime.texi
by Luke Gorrie 08 Apr '05

08 Apr '05

[Did this post not make it to the list yesterday?] heller(a)common-lisp.net (Helmut Eller) writes: > Modified Files: > slime.texi > Log Message: > Mention Unicode support and some multi-threading issues. Cool. I added some notes about the new inspector. I wonder if we're actually using the INSPECTOR argument to INSPECT-IN-EMACS anywhere? Can we remove it, or? I also documented slime-selector. I'm reproducing that section here since it's so bad that most people probably don't know about it: 6.1 `slime-selector' ==================== The `slime-selector' command is for quickly switching to important buffers: the REPL, SLDB, the Lisp source you were just hacking, etc. Once invoked the command prompts for a single letter to specify which buffer it should display. Here are some of the options: `?' A help buffer listing all `slime-selectors''s available buffers. `r' The REPL buffer for the current SLIME connection. `d' The most recently activated SLDB buffer for the current connection. `l' The most recently visited `lisp-mode' source buffer. `s' The `*slime-scratch*' buffer. *Note slime-scratch::. `slime-selector' doesn't have a key binding by default but we suggest that you assign it a global one. You can bind `C-c s' like this: (global-set-key "\C-cs" 'slime-selector) And then you can switch to the REPL from anywhere with `C-c s r'. The macro `def-slime-selector-method' can be used to define new buffers for `slime-selector' to find.

7 17

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 07 Apr '05

07 Apr '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.660 slime/ChangeLog:1.662 --- slime/ChangeLog:1.660 Tue Apr 5 15:41:23 2005 +++ slime/ChangeLog Thu Apr 7 12:00:40 2005 @@ -1,3 +1,10 @@ +2005-04-07 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-net-coding-system): More fixes for + non-mule-XEmacsen. + (slime-net-coding-system): Even more fixes to make it for + mule-XEmacs. + 2005-04-05 Juergen Gmeiner <gj(a)gjdv.at> * swank-lisworks.lisp (find-top-frame): If we can't find an

1 0

[slime-devel] problem with lambda gtk ?
by Nicolas Lamirault 07 Apr '05

07 Apr '05

hello, i have a problem with slime and lambda gtk i make a new sbcl.core image and when i start sbcl from shell with this image, i haven't got any problems : * sbcl --core ./sbcl-af.core This is SBCL 0.8.19.39, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * now i would like to use this new image with slime : C-u M-x slime Run lisp: sbcl --core /home/nicolas/src/lambdagtk/sbcl-af.core BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * ; loading #P"/home/nicolas/src/slime/swank-loader.lisp" ;; loading #P"/home/nicolas/.slime/fasl/sbcl-0.8.19.39-linux-x86/swank-backend.fasl" ;; loading #P"/home/nicolas/.slime/fasl/sbcl-0.8.19.39-linux-x86/nregex.fasl" ;; loading #P"/home/nicolas/.slime/fasl/sbcl-0.8.19.39-linux-x86/swank-sbcl.fasl" debugger invoked on a SB-INT:EXTENSION-FAILURE in thread 9177: Don't know how to REQUIRE SB-BSD-SOCKETS. See also: The SBCL Manual, Variable SB-EXT:*MODULE-PROVIDER-FUNCTIONS* The SBCL Manual, Function REQUIRE 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. (SB-IMPL::REQUIRE-ERROR 3 "Don't know how to ~S ~A.")[:EXTERNAL] 0] any idea ? -- Nicolas Lamirault

3 3

[slime-devel] Fix for missing find-coding-system
by James McIlree 07 Apr '05

07 Apr '05

> Nathan Froyd <froydnj <at> cs.rice.edu> writes: > > > I'm running XEmacs 21.4.15 on OS X 10.3.8. I just updated my Slime > > to the newest, shiniest CVS version (from 1.0 or so), only to find > out > > that it won't work with my XEmacs. Near as I can tell, it's because > > my XEmacs isn't MULE-ized ({make,find}-coding-system do not exist) > and > > Slime really wants MULE or some semblance thereof to operate. I > > assume then that Slime does not support non-MULE emacsen...is this a > > correct assumption? > > The assumption is correct, but it's not much work to remove any > dependency on those functions. It should suffice, to provide dummy > functions for find-coding-system and check-coding-system which return > true for 'binary, and maybe a (if (fboundp 'set-process-coding-system)) > in slime-open-stream-to-lisp. > > I can't try a non-mule version myself, because the Debian "nomule" > versions still have find-coding-system. Also, if I configure CVS > XEmacs with --disable-mule, I still get find-coding-system as a > built-in function. > > Helmut. I ran exactly the same problem yesterday. After some experimentation, I found that xemacs 21.4.17 (latest stable) also does not define find-coding-system. When I built 21.4.17 with mule enabled, something in the font system became confused, making that an unpleasant fix. Xemacs 21.5.20 (beta) does define find-coding-system by default. To build on OS X, you need to specify --without-ldap to configure. I decided to stick with 21.4, and hacked the suggested diffs into slime.el. I'm a novice lisp coder, and a total novice to SLIME coding, so please feel free to change as needed to conform to good coding and style standards! I've tested with ACL & SBCL on OS X 10.3.8, and things started up and minimally worked without trouble. James McIlree diff -r1.478 slime.el 1491a1492,1507 > (if (not (fboundp 'find-coding-system)) > (defun find-coding-system (coding-system) > (if (eq coding-system 'binary) > coding-system > nil))) > > (if (not (fboundp 'check-coding-system)) > (defun check-coding-system (coding-system) > (if (eq coding-system 'binary) > coding-system > nil))) > > (if (not (fboundp 'process-coding-system)) > (defun process-coding-system (unused-and-ignored) > '(binary . binary))) > 2481,2483c2497,2500 < (set-process-coding-system stream < slime-net-coding-system < slime-net-coding-system) --- > (when (fboundp 'set-process-coding-system) > (set-process-coding-system stream > slime-net-coding-system > slime-net-coding-system))

4 3

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 05 Apr '05

05 Apr '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.659 slime/ChangeLog:1.660 --- slime/ChangeLog:1.659 Mon Apr 4 08:16:23 2005 +++ slime/ChangeLog Tue Apr 5 15:41:23 2005 @@ -1,3 +1,8 @@ +2005-04-05 Juergen Gmeiner <gj(a)gjdv.at> + + * swank-lisworks.lisp (find-top-frame): If we can't find an + invoke-debugger frame we take any old frame at the top. + 2005-04-04 James McIlree <ovrskeek(a)mac.com> * slime.el (find-coding-system, check-coding-system)

1 0

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 04 Apr '05

04 Apr '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.657 slime/ChangeLog:1.659 --- slime/ChangeLog:1.657 Fri Apr 1 23:57:42 2005 +++ slime/ChangeLog Mon Apr 4 08:16:23 2005 @@ -1,3 +1,30 @@ +2005-04-04 James McIlree <ovrskeek(a)mac.com> + + * slime.el (find-coding-system, check-coding-system) + (process-coding-system, set-process-coding-system): Dummy + functions for no-mule-XEmacsen. + +2005-04-04 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-repl-show-maximum-output): New + function. Immitate the scrolling behavior of a terminal. + (slime-with-output-end-mark, slime-repl-return) + (slime-repl-send-input, slime-display-output-buffer): Use it + (slime-lisp-implementation-version, slime-machine-instance): New + connection variables. Suggested by Eduardo Muñoz. + (slime-set-connection-info): Initialize them. + + * swank.lisp (connection-info): Include version and hostname in + the result. + + * swank-cmucl.lisp (breakpoint-values): Fixes for CMUCL-2005-03 + snapshot. + + * doc/slime.texi: Fix spelling errors. + + * cl-indent.el: Remove the file. Let the Emacs developers + maintain it. + 2005-04-01 Helmut Eller <heller(a)common-lisp.net> * slime.el (sldb-get-buffer): Initialize the buffer local

1 0

[slime-devel] SLIME and Allegro on Windows
by Peter Seibel 04 Apr '05

04 Apr '05

Does anyone know what the deal is with using Allegro on Windows with SLIME? As in, why it doesn't Just Work. (I've seen Bill Clementson's blog entry--that's the approved work around, right?) Is this something that Franz could fix by providing a console app version of alisp.exe (and one that doesn't have whatever multithreading problem build.exe (the console app version of mlisp.exe) has?) -Peter -- Peter Seibel peter(a)gigamonkeys.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

2 1

[slime-devel] small patch to slime-xref-quit & feature request.
by Eduardo Muñoz 04 Apr '05

04 Apr '05

Using M-. with a generic function presents a buffer selection thingy. Selecting the desired method or defclass opens the desired buffer but then using q to exit the xrefs buffer restores de window configuration so I have to select the buffer manually. Using C-x o to exit the xref buffer leaves it visible but this is something I want to avoid. So I have installed locally the following patch: Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.477 diff -u -r1.477 slime.el --- slime.el 1 Apr 2005 19:58:20 -0000 1.477 +++ slime.el 1 Apr 2005 21:07:24 -0000 @@ -6065,12 +6066,14 @@ (error "No context for finding locations.")) (funcall slime-next-location-function)) -(defun slime-xref-quit () - "Kill the current xref buffer and restore the window configuration." - (interactive) +(defun slime-xref-quit (arg) + "Kill the current xref buffer and restore the window configuration. +If arg is supplied do not restore configuration." + (interactive "P") (let ((config slime-xref-saved-window-configuration)) (slime-xref-cleanup) - (set-window-configuration config))) + (unless arg + (set-window-configuration config)))) (defun slime-xref-cleanup () "Delete overlays created by xref mode and kill the xref buffer." ---------------------------- The feature request is to send more arguments to slime-translate-to-lisp-filename-function and her sister slime-translate-from-lisp-filename-function, say (lisp-implementation-version) and (machine-instance). I am no elisp expert and failed to work out something like this. The idea is to be able to know if the translation is really needed (emacs on windows, lisp on linux) or not (everything on linux). The easy part is to know where emacs is running and the hard one (that I leave to fine slime hackers :) is to know the lisp host environment. Greetings, -- Eduardo Muñoz | (prog () 10 (print "Hello world!") http://213.97.131.125/ | 20 (go 10))

3 4

[slime-devel] GCL and slime
by Pekka NIiranen 03 Apr '05

03 Apr '05

Hi, why is GCL (http://savannah.gnu.org/projects/gcl/) not supported? -pekka-

3 2

[slime-devel] Daily ChangeLog diff
by lgorrie＠common-lisp.net 01 Apr '05

01 Apr '05

Index: slime/ChangeLog diff -u slime/ChangeLog:1.651 slime/ChangeLog:1.657 --- slime/ChangeLog:1.651 Sun Mar 27 21:42:54 2005 +++ slime/ChangeLog Fri Apr 1 23:57:42 2005 @@ -1,3 +1,57 @@ +2005-04-01 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (sldb-get-buffer): Initialize the buffer local + variables slime-buffer-connection and slime-current-thread when + creating a fresh buffer. + + * swank.lisp (spawn-repl-thread): Use + *default-worker-thread-bindings* just like spawn-worker-thread. + (wrap-sldb-vars): New function. Rebind *sldb-level* to avoid + confusion with recursive errors during eval-in-frame. + (eval-string-in-frame, pprint-eval-string-in-frame): Use it. + + * swank-allegro.lisp (eval-in-frame): Allegro's + eval-form-in-context does nothing special with lexical variables + in the frame. Wrap an explicit LET around the form to get similar + behavior as in the other Lisps. + (inspect-for-emacs (structure-object)): Remove structure related + methods. It's already covered by the general case with + allegro-inspect. + (common-seperated-spec): Deleted + +2005-04-01 Luke Gorrie <luke(a)synap.se> + + * slime.el (slime-xref-mode): Summarise the most important + bindings in the mode description. + + * metering.lisp: Now supports only CLISP and OpenMCL. + Removed a lot of really ugly reader-conditionalized code, much of + it for archaic lisps (#+cltl2, #+lcl3.0, #+mcl1.3.2, etc). + + * swank-source-path-parser.lisp (check-source-path): Signal an + error if a source path is malformed. SBCL sometimes gives (NIL). + (source-path-stream-position): Use it. + + * slime.el (slime-goto-definition): Handle :error locations here + before any window/buffer changes are made. + +2005-04-01 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> + + * slime.el (slime-keys): Bind slime-edit-definition-other-window + to `C-x 4 .' and slime-edit-definition-other-frame to `C-x 5 .', + shadowing the equivalent find-tag... bindings. + (slime-goto-definition): In the other-window and other-frame cases, + make sure point does not move in the originating window, even when + the definition is found in the same buffer. + +2005-03-31 Luke Gorrie <luke(a)synap.se> + + * doc/slime.texi (slime-selector): New section. + (Inspector): Updated for the post-1.0 inspector. + + * slime.el (slime-selector): Removed unneeded "the" prefixes in + descriptions of what the selector methods do. + 2005-03-27 Helmut Eller <heller(a)common-lisp.net> * PROBLEMS, NEWS, doc/slime.texi: Some updates for the upcoming

1 0

[slime-devel] [Patch] Improve slime-edit-definition-other-window and ...-frame
by Matthias Koeppe 01 Apr '05

01 Apr '05

Hi, I am sending a little patch that improves the commands slime-edit-definition-other-window and ...-frame. Would someone like to merge it into CVS? Cheers, Matthias 2005-03-27 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> * slime.el (slime-keys): Bind slime-edit-definition-other-window to `C-x 4 .' and slime-edit-definition-other-frame to `C-x 5 .', shadowing the equivalent find-tag... bindings. (slime-goto-definition-other-window-aux): New function, adapted from the Emacs function find-tag-other-window. (slime-goto-definition): In the other-window and other-frame cases, make sure point does not move in the originating window, even when the definition is found in the same buffer. --- slime.el.~1.473.~ 2005-03-27 16:35:04.000000000 +0200 +++ slime.el 2005-03-27 17:02:06.000000000 +0200 @@ -555,6 +555,8 @@ ("\C-i" slime-complete-symbol :prefixed t :inferior t) ("\M-i" slime-fuzzy-complete-symbol :prefixed t :inferior t) ("\M-." slime-edit-definition :inferior t :sldb t) + ("\C-x4." slime-edit-definition-other-window :inferior t :sldb t) + ("\C-x5." slime-edit-definition-other-frame :inferior t :sldb t) ("\M-," slime-pop-find-definition-stack :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) @@ -5122,18 +5124,41 @@ (error "No known definition for: %s" name)) (slime-goto-definition name definitions where)))) +(defun slime-goto-definition-other-window-aux (definition) + ;; Taken from the Emacs function `find-tag-other-window': + ;; This hair is to deal with the case where the tag is found in the + ;; selected window's buffer; without the hair, point is moved in both + ;; windows. To prevent this, we save the selected window's point before + ;; doing find-tag-noselect, and restore it after. + (let ((window-point (window-point (selected-window)))) + (slime-goto-source-location (slime-definition.location + definition)) + (let ((tagbuf (current-buffer)) + (tagpoint (point))) + (set-window-point (prog1 + (selected-window) + (switch-to-buffer-other-window tagbuf) + ;; We have to set this new window's point; it + ;; might already have been displaying a + ;; different portion of tagbuf, in which case + ;; switch-to-buffer-other-window doesn't set + ;; the window's point from the buffer. + (set-window-point (selected-window) tagpoint)) + window-point)))) + (defun slime-goto-definition (name definitions &optional where) (slime-push-definition-stack) (cond ((slime-length> definitions 1) (slime-show-definitions name definitions)) (t - (slime-goto-source-location (slime-definition.location - (car definitions))) (cond ((equal where 'window) - (switch-to-buffer-other-window (current-buffer))) + (slime-goto-definition-other-window-aux (car definitions))) ((equal where 'frame) - (switch-to-buffer-other-frame (current-buffer))) + (let ((pop-up-frames t)) + (slime-goto-definition-other-window-aux (car definitions)))) (t + (slime-goto-source-location (slime-definition.location + (car definitions))) (switch-to-buffer (current-buffer))))))) (defun slime-edit-definition-other-window (name) -- Matthias Koeppe -- http://www.math.uni-magdeburg.de/~mkoeppe

2 6