slime-devel August 2004

slime-devel@common-lisp.net

33 participants
49 discussions

[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

[slime-devel] Is there some way to disconnect from SWANK quit emacs, and then reconect back without restarting SWANK?
by Ignas Mikalajūnas 16 Aug '04

16 Aug '04

I have tried doing this in several implementations: sbcl 8.7 sbcl 8.11 cmucl 19a cmucl 18e and failed all the time. slime-disconnect or slime-quit both make me reastart the swank by hand from lisp repl directly. Ignas Mikalajunas

3 2

[slime-devel] Allegro Doc Lookup
by Thomas Schilling 16 Aug '04

16 Aug '04

This is a (dirty) little hack to open the allegro docs from within Slime: (defun allegro-doc-lookup (symbol) (interactive (list (slime-read-symbol-name "Allegro Doc for: "))) (slime-eval-async `(cg:eval-in-listener-thread '(cl:let ((wnd (cl:make-instance 'cg:text-edit-window :name :get-help :owner (cg:screen cg:*system*) :state :shrunk :border :frame))) (cl:format (cg:frame-child wnd) "~a" ',symbol) (devel::windows-help-command wnd) (cl:close wnd))))) I didn't know where to integrate this in Slime (if even) so I thought this would be the best place to post it to. -ts

1 0

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

15 Aug '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.503 slime/ChangeLog:1.504 --- slime/ChangeLog:1.503 Fri Aug 13 14:27:08 2004 +++ slime/ChangeLog Sat Aug 14 15:10:20 2004 @@ -1,3 +1,8 @@ +2004-08-14 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * slime.el (slime-find-buffer-package): Use "%s", not "%S", to + avoid ugly escape characters, if the package name contains dots. + 2004-08-13 Luke Gorrie <luke(a)bluetail.com> * slime.el (sldb-eval-in-frame): Print result to the REPL when a

1 0

[slime-devel] slime-eval-last-expression in REPL
by Michael Weber 14 Aug '04

14 Aug '04

Calling C-x C-e (M-x slime-eval-last-expression) at a bare REPL prompt causes this: The variable CL-USER> is unbound. [Condition of type UNBOUND-VARIABLE] Restarts: 0: [ABORT] Abort handling SLIME request. 1: [DESTROY-THREAD] Destroy this thread (12715) GNU Emacs 21.3.50.1 SLIME CVS 2004/08/13 Cheers, Michael

2 1

[slime-devel] SB-EXT:RUN-PROGRAM and *STANDARD-OUTPUT* interaction in REPL
by Michael Weber 14 Aug '04

14 Aug '04

[Apologies, if this hit the list twice.] There seems to be some SLIME interaction between SBCL's SB-EXT:RUN-PROGRAM and *STANDARD-OUTPUT*. Consider this: (defun test (stream) (let* ((p (sb-ext:run-program "tr" '("a-z" "n-za-m") :input :stream :output stream :search t :wait nil)) (in (sb-ext:process-input p))) (format in "test~%") (sb-ext:process-close p) (sb-ext:process-wait p))) Executing (TEST T) causes the output go to emacs' *inferior-lisp* buffer, with (TEST *STANDARD-OUTPUT*) it goes to SLIME's REPL buffer, although they should behave the same, AFAICT. GNU Emacs 21.3.50.1 SLIME CVS-2004/08/13 SBCL 0.8.13 (I understand that this could just as well be an SBCL issue.) Now, why this function hangs after executing is another thing which I haven't figured out yet, but this is likely due to wrong use... Cheers, Michael

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel August 2004