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