August 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] eval-in-emacs and 'window'-debugger
by Antonio Menezes Leitao 10 Feb '05

10 Feb '05

Hi everybody, I noticed that slime provides a function eval-in-emacs that sends a form to the emacs side where it is evaluated. However, I would like to get the results on the lisp side but I always get NIL. Is there a different swank function for that? (in the emacs-lisp-interface from Franz I used a lep::eval-in-emacs that did precisely what I needed). This is very useful to provide refactoring operations (that operate on the Lisp side) that need to interact with the user using emacs lisp operations such as y-or-n-p or read-from-minibuffer. I know that it might be difficult to find a general scheme to translate from emacs lisp values to common lisp values but all I need is symbols, strings, numbers and such. ----------------- A few years ago I developed a 'window'-debugger and 'window'-inspector for Ilisp+CMUCL similar to what I used in the Explorer Lisp Machines. I recently adapted it to Slime+Whatever-Common-Lisp-slime-supports. If anyone is interested I can post it. However, I would like to suggest two changes to Slime in order to improve its portability: 1. The function swank::inspected-parts should provide a recognizable value for unbound slots. Here is one example in SBCL CL-USER> (defclass c () ((a))) #<STANDARD-CLASS C> CL-USER> (swank::inspected-parts (make-instance 'c)) "The object is a STANDARD-OBJECT of type C. " (("A" . #:INSPECT-UNBOUND-OBJECT-3530)) and in CLISP CL-USER> (swank::inspected-parts (make-instance 'c)) "#<COMMON-LISP-USER::C #x20426856> standard object type: COMMON-LISP-USER::C" (("A" . INSPECT-TMP-PACKAGE-5413::|#<unbound>|)) I know that the returned values are recognizable (e.g., by being the value of the variable sb-impl::*inspect-unbound-object-marker* or something similar) but given the fact that it depends on the Common Lisp being used, it would be preferable if Slime provided a function that recognizes such value. If it already does, my apologies. 2. The function swank::frame-locals doesn't distinguish valid locals from invalid ones. I know that not all Common Lisps make that distinction but for the ones that make, it would be useful to get that information (for Common Lisps that don't provide such information a default could be chosen). Currently, Slime puts a :not-available as value which, IMHO, is error-prone. It would be nicer to have an extra field for each local that describes its status or (as in 1.) a slime function that recognizes such special value or as a third (and not so good) alternative, swank::frame-locals should not produce invalid locals. Thanks in advance, António Leitão.

2 2

[slime-devel] simple-base-string declarations
by Christophe Rhodes 31 Aug '04

31 Aug '04

Hi, In a number of places in swank.lisp various strings are declared as SIMPLE-BASE-STRING. Is there a reason for this declaration -- in particular, is it expected that these strings will be specialized to hold only BASE-CHAR? Or are they in fact general strings? (at least the version in BRIEFLY-DESCRIBE-SYMBOL-FOR-EMACS leads me to suspect that they are fairly general strings). If I'm right, could the declaration be changed to reflect this, maybe to SIMPLE-STRING (or even STRING, if they're not in performance-critical areas)? It is likely that sbcl, in the near future, will have multiple string representations, where SIMPLE-BASE-STRING means (SIMPLE-ARRAY BASE-CHAR (*)), which will be distinct from (SIMPLE-ARRAY CHARACTER (*)) [ they're currently the same in all known implementations, I believe]. Cheers, Christophe -- http://www-jcsu.jesus.cam.ac.uk/~csr21/ +44 1223 510 299/+44 7729 383 757 (set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b))) (defvar b "~&Just another Lisp hacker~%") (pprint #36rJesusCollegeCambridge)

2 2

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 31 Aug '04

31 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.510 slime/ChangeLog:1.511 --- slime/ChangeLog:1.510 Sat Aug 28 04:27:08 2004 +++ slime/ChangeLog Tue Aug 31 00:34:24 2004 @@ -1,3 +1,19 @@ +2004-08-30 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * PROBLEMS: We require SBCL 0.8.13. 0.8.12 is no longer + supported. + + * swank-allegro.lisp (find-fspec-location): Catch errors in + excl:source-file. + + * swank.lisp (send-to-socket-io): Add some ignore declarations. + + * slime.el (sldb-fetch-all-frames, sldb-end-of-backtrace) + (sldb-beginning-of-backtrace): New commands. + (slime-search-suppressed-forms): Change the start regexp so that + reader conditionals in single line comments, like "; #+foo", are + ignored. + 2004-08-27 Peter Seibel <peter(a)javamonkey.com> * swank-backend.lisp (swank-compile-string): Add directory @@ -20,8 +36,8 @@ 2004-08-18 Matthew Danish <mrd+nospam(a)cmu.edu> - * slime/swank-allegro.lisp (swank-compile-string): Use #\; instead - of #\: to separate the position from the buffer-name. This avoids + * swank-allegro.lisp (swank-compile-string): Use #\; instead of + #\: to separate the position from the buffer-name. This avoids troubles on Windows. 2004-08-16 Luke Gorrie <luke(a)bluetail.com>

1 0

[slime-devel] MOP access
by Rui Patrocínio 31 Aug '04

31 Aug '04

Hi, Is there any access to MOP-like functionality in swank? I've not found it so I create a simple interface, similar to the xref one. swank.lisp: ;;; MOP (defslimefun mop (type symbol-name) (let ((symbol (parse-symbol-or-lose symbol-name *buffer-package*))) (ecase type (:subclasses (class-direct-subclasses symbol)) (:superclasses (class-direct-superclasses symbol))))) Maybe 'mop' isn't the best name. swank-backend.lisp: ;;; MOP (definterface class-direct-subclasses (class-name) "Return the list of subclasses of class.") (definterface class-direct-superclasses (class-name) "Return the list of superclasses of class.") swank-cmucl.lisp: ;;; CLOS MOP (defimplementation class-direct-subclasses (class-name) (handler-bind ((simple-error (lambda (c) (declare (ignore c)) (return-from class-direct-subclasses nil)))) (let* ((class (find-class class-name)) (subclasses (pcl:class-direct-subclasses class))) (mapcar #'(lambda (x) (symbol-name (pcl:class-name x))) subclasses)))) (defimplementation class-direct-superclasses (class-name) (handler-bind ((simple-error (lambda (c) (declare (ignore c)) (return-from class-direct-superclasses nil)))) (let* ((class (find-class class-name)) (superclasses (pcl:class-direct-superclasses class))) (mapcar #'(lambda (x) (symbol-name (pcl:class-name x))) superclasses)))) The handler is to catch the errors of find-class with a class that doesn't exist. Maybe there's a better behaviour in that situation. I have a generic browser in emacs that can be used to see the stuff above, xrefs,etc. I'll release the code soon. Rui Patrocínio

2 1

[slime-devel] Bug report and bug reporting
by smishra＠speakeasy.net 30 Aug '04

30 Aug '04

Hi, I've encountered a bug when using slime with ACL 6.2 on windows. I get an error if in my slime repl I run (tpl:do-command "zoom"). Is this replicable? Any suggestions? Also, is there any mechanism to report slime bugs other than subscribing to this mailing list? I've never used gmane, is it less of a hassle for the end user? Perhaps a note to that effect would be good on the web page. But I feel there ought to be something on the web page or documentation that says something about bug reporting while slime is still imperfect. Thanks! Sunil

4 4

[slime-devel] how to see the full backtrace???
by Pascal J.Bourguignon 30 Aug '04

30 Aug '04

I've got a big backtrace. Of couse in these cases, the interesting part is deep down at the beginning of the recursion. So, bar from spending two hours scrolling down line by line, (I've already spent 3 minutes and I only got 838 frames, how can I get it to show the full backtrace at once? -- __Pascal Bourguignon__ http://www.informatimago.com/ Our enemies are innovative and resourceful, and so are we. They never stop thinking about new ways to harm our country and our people, and neither do we.

2 2

Re: [slime-devel] how to see the full backtrace???
by Bill_Clementson＠peoplesoft.com 29 Aug '04

29 Aug '04

Pascal J.Bourguignon <pjb(a)informatimago.com> writes: > I've got a big backtrace. Of couse in these cases, the interesting > part is deep down at the beginning of the recursion. > > So, bar from spending two hours scrolling down line by line, (I've > already spent 3 minutes and I only got 838 frames, how can I get it to > show the full backtrace at once? One option is to press "B" (sldb-break-with-default-debugger) in the sldb buffer - that will take you to the default debugger in the repl buffer and you will no longer be subject to the constraints of sldb. - Bill Clementson

1 0

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

28 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.509 slime/ChangeLog:1.510 --- slime/ChangeLog:1.509 Mon Aug 23 11:57:45 2004 +++ slime/ChangeLog Sat Aug 28 04:27:08 2004 @@ -1,3 +1,9 @@ +2004-08-27 Peter Seibel <peter(a)javamonkey.com> + + * swank-backend.lisp (swank-compile-string): Add directory + argument which is used by Allegro backend to improve source + recording for definitions compiled with C-c C-c. + 2004-08-23 John Paul Wallington <jpw(a)gnu.org> * slime.el (slime-pretty-package-name): Fix last cond clause.

1 0

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 27 Aug '04

27 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.509 slime/ChangeLog:1.510 --- slime/ChangeLog:1.509 Mon Aug 23 11:57:45 2004 +++ slime/ChangeLog Sat Aug 28 04:27:08 2004 @@ -1,3 +1,9 @@ +2004-08-27 Peter Seibel <peter(a)javamonkey.com> + + * swank-backend.lisp (swank-compile-string): Add directory + argument which is used by Allegro backend to improve source + recording for definitions compiled with C-c C-c. + 2004-08-23 John Paul Wallington <jpw(a)gnu.org> * slime.el (slime-pretty-package-name): Fix last cond clause.

1 0

[slime-devel] Better solution to redefinition warnings in Allegro
by Peter Seibel 27 Aug '04

27 Aug '04

Since my last attempt (a couple weeks ago) was totally bogus I tried again. Here's my latest attempt. I wanted to check whether there was anything about this version that was as busted as my previous attempt before I made the corresponding changes to the other backends. The basic idea is that we pass a new argument to swank-compile-string containing the directory of the file of the buffer from which we are compiling (when there is one). In the Allegro backend we bind *DEFAULT-PATHNAME-DEFAULTS* to this directory so that the source recording mechanism thinks the file it is recording is in that directory. Then you can add something like this to one's .swank.lisp to make Allegro ignore the :<position> part of the recorded location. #+allegro (setf excl::*redefinition-pathname-comparison-hook* (list #'(lambda (old new obj type) (declare (ignore obj type)) (cond ((string= (namestring old) (let ((str (namestring new))) (subseq str 0 (position #\: str :from-end t))))))))) Here's the patch; please let me know what you think. -Peter Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.392 diff -u -r1.392 slime.el --- slime.el 16 Aug 2004 21:41:35 -0000 1.392 +++ slime.el 17 Aug 2004 15:32:21 -0000 @@ -3147,7 +3147,7 @@ (defun slime-compile-string (string start-offset) (slime-eval-async - `(swank:compile-string-for-emacs ,string ,(buffer-name) ,start-offset) + `(swank:compile-string-for-emacs ,string ,(buffer-name) ,start-offset ,(if (buffer-file-name) (file-name-directory (buffer-file-name)))) (slime-compilation-finished-continuation))) (defvar slime-hide-style-warning-count-if-zero t) @@ -7157,7 +7157,7 @@ ("swank::emacs-connected" "(swank::emacs-connected stream)") ("swank::compile-string-for-emacs" - "(swank::compile-string-for-emacs string buffer position)") + "(swank::compile-string-for-emacs string buffer position directory)") ("swank::connection.socket-io" "(swank::connection.socket-io \$struct\\(ure\$?\\|object\\|instance\\))") ("cl:lisp-implementation-type" Index: swank-allegro.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-allegro.lisp,v retrieving revision 1.49 diff -u -r1.49 swank-allegro.lisp --- swank-allegro.lisp 4 Aug 2004 17:17:55 -0000 1.49 +++ swank-allegro.lisp 17 Aug 2004 15:32:21 -0000 @@ -239,14 +239,15 @@ (when binary-filename (delete-file binary-filename)))))) -(defimplementation swank-compile-string (string &key buffer position) +(defimplementation swank-compile-string (string &key buffer position (directory *default-pathname-defaults*)) ;; We store the source buffer in excl::*source-pathname* as a string ;; of the form <buffername>:<start-offset>. Quite ugly encoding, but ;; the fasl file is corrupted if we use some other datatype. (with-compilation-hooks () (let ((*buffer-name* buffer) (*buffer-start-position* position) - (*buffer-string* string)) + (*buffer-string* string) + (*default-pathname-defaults* (merge-pathnames (pathname directory)))) (compile-from-temp-file (format nil "~S ~S~%~A" `(in-package ,(package-name *package*)) Index: swank-backend.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-backend.lisp,v retrieving revision 1.63 diff -u -r1.63 swank-backend.lisp --- swank-backend.lisp 30 Jul 2004 21:44:05 -0000 1.63 +++ swank-backend.lisp 17 Aug 2004 15:32:21 -0000 @@ -191,14 +191,17 @@ (declare (ignore ignore)) `(call-with-compilation-hooks (lambda () (progn ,@body)))) -(definterface swank-compile-string (string &key buffer position) +(definterface swank-compile-string (string &key buffer position directory) "Compile source from STRING. During compilation, compiler conditions must be trapped and resignalled as COMPILER-CONDITIONs. If supplied, BUFFER and POSITION specify the source location in Emacs. Additionally, if POSITION is supplied, it must be added to source -positions reported in compiler conditions.") +positions reported in compiler conditions. + +And if DIRECTORY is specified it is bound as the value of +*DEFAULT-PATHNAME-DEFAULTS*.") (definterface operate-on-system (system-name operation-name &rest keyword-args) "Perform OPERATION-NAME on SYSTEM-NAME using ASDF. Index: swank.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank.lisp,v retrieving revision 1.222 diff -u -r1.222 swank.lisp --- swank.lisp 13 Aug 2004 16:14:13 -0000 1.222 +++ swank.lisp 17 Aug 2004 15:32:22 -0000 @@ -1505,13 +1505,13 @@ Record compiler notes signalled as `compiler-condition's." (swank-compiler (lambda () (swank-compile-file filename load-p)))) -(defslimefun compile-string-for-emacs (string buffer position) +(defslimefun compile-string-for-emacs (string buffer position directory) "Compile STRING (exerpted from BUFFER at POSITION). Record compiler notes signalled as `compiler-condition's." (with-buffer-syntax () (swank-compiler (lambda () - (swank-compile-string string :buffer buffer :position position))))) + (swank-compile-string string :buffer buffer :position position :directory directory))))) (defslimefun operate-on-system-for-emacs (system-name operation &rest keywords) "Compile and load SYSTEM using ASDF. -- Peter Seibel peter(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

3 8

[slime-devel] minor nit -- request
by Sundar Narasimhan 27 Aug '04

27 Aug '04

When I eval in frame .. if I mistype or stimulate another debug entry somehow, it's somewhat annoying when I pop back to the previous debugger level, the cursor moves to the 0'th frame.. wouldn't it be nicer if it stayed at the frame level where I was? (or am I missing the common idiom here?)

2 1

[slime-devel] slime 1.0 plan, party
by Luke Gorrie 23 Aug '04

23 Aug '04

Ahoy, The new plan is to release slime 1.0 on saturday the 4th of september. The release party will be in Cesky Krumlov (*) in the Czech republic (near the Austrian border) on the same day. See you all there! :-) (*) http://www.virtourist.com/europe/krumlov/ P.S., from today my email address is luke(a)member.fsf.org

1 0

[slime-devel] slime-pretty-package-name buglet
by John Paul Wallington 23 Aug '04

23 Aug '04

The byte-compiler noticed this: Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.392 diff -u -r1.392 slime.el --- slime.el 16 Aug 2004 21:41:35 -0000 1.392 +++ slime.el 23 Aug 2004 00:09:40 -0000 @@ -434,7 +434,7 @@ "Return a pretty version of a package name designator (as a string)." (cond ((string-match "^:\$.*\$$" name) (match-string 1 name)) ((string-match "^\"\$.*\$\"$" name) (match-string 1 name)) - ((t name)))) + (t name))) (when slime-update-modeline-package (run-with-idle-timer 0.2 0.2 'slime-update-modeline-package)) 2004-08-23 John Paul Wallington <jpw(a)gnu.org> * slime.el (slime-pretty-package-name): Fix last cond clause.

2 1

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 21 Aug '04

21 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.507 slime/ChangeLog:1.508 --- slime/ChangeLog:1.507 Thu Aug 19 07:53:46 2004 +++ slime/ChangeLog Fri Aug 20 18:38:17 2004 @@ -1,3 +1,8 @@ +2004-08-21 Luke Gorrie <luke(a)bluetail.com> + + * swank.lisp (*global-debugger*): New configurable to globally + install swank-debugger-hook as *debugger-hook*. True by default. + 2004-08-19 Luke Gorrie <luke(a)bluetail.com> * doc/slime.texi: C-c C-c C-a, C-c C-u C-e.

1 0

[slime-devel] XREF for SBCL
by Nikodemus Siivola 21 Aug '04

21 Aug '04

The attached patch + new file hooks the PXREF to SBCL as well, sharing code with the Clisp backend. To make usage a bit less tedious I hooked PXREF:XREF-FILE into swank-compile-file. Clisp hasn't been tested after these changes, and neither has SBCL been subjected to much pounding, but "seems to work". To make the pxref more useful it might make sense to save the collected db on exits and load on startup... Also, an xref-op for asdf would not come amiss. (Just noting these out loud in case someone has nothing to do over the weekend.) Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs."

1 0

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 20 Aug '04

20 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.506 slime/ChangeLog:1.507 --- slime/ChangeLog:1.506 Wed Aug 18 14:21:52 2004 +++ slime/ChangeLog Thu Aug 19 07:53:46 2004 @@ -1,3 +1,8 @@ +2004-08-19 Luke Gorrie <luke(a)bluetail.com> + + * doc/slime.texi: C-c C-c C-a, C-c C-u C-e. + Thanks Barry Fishman for reporting incorrect indexing. + 2004-08-18 Matthew Danish <mrd+nospam(a)cmu.edu> * slime/swank-allegro.lisp (swank-compile-string): Use #\; instead

1 0

[slime-devel] [PATCH} Problem with Restart node in slime.texi
by Barry Fishman 19 Aug '04

19 Aug '04

Version 4.7 makeinfo fails with case problems when referencing "Restarts" node as "restarts" in menus. Fix actually performed by Emacs texinfo mode by selecting "Texinfo/Update All Menus" from menubar. -- Barry Fishman

2 1

[slime-devel] Problem with SLIME + CMUCL + CLSQL + Oracle
by Ivan Toshkov 19 Aug '04

19 Aug '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm using recently updated version of SLIME, CMUCL 19a, CLSQL 3 and Oracle 8.1.7, everything on linux (Red Hat Enterprise Server 3). I do: CL-USER> (asdf:oos 'asdf:load-op :clsql-oracle) CL-USER> (use-package :clsql-user) CL-USER> (connect '("SID" "user" "pass") :database-type :oracle) At this point CMUCL starts using the processor on >90% and stays that way untill killed. I've tried the same dialog without SLIME and it works fine. Also, I've tried with SQLite instead of Oracle and it works under SLIME. Any ideas? Regards, Ivan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBJGd/uUkHlsKSHdcRAg+NAJ9K7ZXwIpZK1IttTauTgjvxCP0BYwCZATTf q9AkKeWgtZWd/5Z+BWt2Hkw= =/RHQ -----END PGP SIGNATURE-----

2 4

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 19 Aug '04

19 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.505 slime/ChangeLog:1.506 --- slime/ChangeLog:1.505 Mon Aug 16 14:44:18 2004 +++ slime/ChangeLog Wed Aug 18 14:21:52 2004 @@ -1,3 +1,9 @@ +2004-08-18 Matthew Danish <mrd+nospam(a)cmu.edu> + + * slime/swank-allegro.lisp (swank-compile-string): Use #\; instead + of #\: to separate the position from the buffer-name. This avoids + troubles on Windows. + 2004-08-16 Luke Gorrie <luke(a)bluetail.com> * doc/slime.texi: Random updates.

1 0

[slime-devel] swank-compile-string and xref info in Allegro
by Matthew Danish 18 Aug '04

18 Aug '04

Using the syntax "buffer-name:position" under Allegro/Win32 seems to be causing all sorts of interesting namestring parsing issues, rending slime-compile-defun useless (among other things). I have changed the syntax to "buffer-name;position". Still a hack, but it works. Index: swank-allegro.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-allegro.lisp,v retrieving revision 1.49 diff -u -r1.49 swank-allegro.lisp --- swank-allegro.lisp 4 Aug 2004 17:17:55 -0000 1.49 +++ swank-allegro.lisp 17 Aug 2004 21:03:45 -0000 @@ -241,7 +241,7 @@ (defimplementation swank-compile-string (string &key buffer position) ;; We store the source buffer in excl::*source-pathname* as a string - ;; of the form <buffername>:<start-offset>. Quite ugly encoding, but + ;; of the form <buffername>;<start-offset>. Quite ugly encoding, but ;; the fasl file is corrupted if we use some other datatype. (with-compilation-hooks () (let ((*buffer-name* buffer) @@ -252,7 +252,7 @@ `(in-package ,(package-name *package*)) `(eval-when (:compile-toplevel :load-toplevel) (setq excl::*source-pathname* - (format nil "~A:~D" ',buffer ',position))) + (format nil "~A;~D" ',buffer ',position))) string))))) ;;;; Definition Finding @@ -275,18 +275,21 @@ ((member :top-level) (list :error (format nil "Defined at toplevel: ~A" (fspec->string fspec)))) (string - (let ((pos (position #\: file))) + (let ((pos (position #\; file :from-end t))) (make-location (list :buffer (subseq file 0 pos)) (list :position (parse-integer (subseq file (1+ pos))))))) (null (list :error (format nil "Unknown source location for ~A" (fspec->string fspec))))))) -(defun fspec->string (fspec &aux (*package* (find-package :keyword))) +(defun fspec->string (fspec) (etypecase fspec - (symbol (prin1-to-string fspec)) - (list (format nil "(method ~A)" - (prin1-to-string (second fspec)))))) + (symbol (let ((*package* (find-package :keyword))) + (prin1-to-string fspec))) + (list (format nil "(~A ~A)" + (prin1-to-string (first fspec)) + (let ((*package* (find-package :keyword))) + (prin1-to-string (second fspec))))))) (defun fspec-definition-locations (fspec) (let ((defs (excl::find-multiple-definitions fspec))) -- ;;;; Matthew Danish -- user: mrd domain: cmu.edu ;;;; OpenPGP public key: C24B6010 on keyring.debian.org

2 1

[slime-devel] newbie questions related to sldb
by Sundar Narasimhan 17 Aug '04

17 Aug '04

First of, thanks to everyone working on this -- slime seems great. Simple question: when the sldb window pops up -- and I type e -- or other evaluation related functions, the interactions occur in the minibuffer -- which doesn't work well for me for forms/results that extend over multiple lines. What's the accepted wisdom wrt. what one could do here? Second, when I type 't' -- sometimes the top frame disappears in sldb -- and my cursor is left at the next frame.. is this a bug? (I'm using cmucl on FC2 via xemacs). Thanks.

2 7

[slime-devel] SLIME showing value of symbol in mini-buffer
by David Steuber 17 Aug '04

17 Aug '04

Hi, I'm not sure what I did to turn on this feature or how to turn it off. When the point is over a symbol in the Lisp buffer, its value is displayed in the mini-buffer. This would normally be fine, but it is a bit of an issue when the symbol is an array with 100,000 elements in it. My machine hates that. I looked in the docs, but I couldn't find what it might be. I do hope this is not part of autodoc mode which I have turned on in my .emacs. Anyway, how do I turn this useful but potentially dangerous feature off? Thanks.

3 4

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 17 Aug '04

17 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.504 slime/ChangeLog:1.505 --- slime/ChangeLog:1.504 Sat Aug 14 15:10:20 2004 +++ slime/ChangeLog Mon Aug 16 14:44:18 2004 @@ -1,3 +1,11 @@ +2004-08-16 Luke Gorrie <luke(a)bluetail.com> + + * doc/slime.texi: Random updates. + + * slime.el (slime-space): Use slime-message instead of + slime-background-message. This displays multi-line arglists. + (sldb-mode-map): Bind 'C' to sldb-inspect-condition. + 2004-08-14 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * slime.el (slime-find-buffer-package): Use "%s", not "%S", to

1 0