slime-devel March 2006

slime-devel@common-lisp.net

43 participants
49 discussions

[slime-devel] Tracing with slime presentations
by Luigi Panzeri 09 Mar '06

09 Mar '06

Hi. i wrote a snippet to do tracing of functions allowing slime presentations (thanks to segv for helping me with present-object). Obviously this code works only on sbcl. (defun present-object (value &key (showvalue value) (printfun #'prin1) (stream *standard-output*)) (swank::presenting-object value stream (funcall printfun showvalue stream)) value) (defmacro present-trace (fun &rest rest) `(trace ,fun ;; present input arguments :print (present-object (let ((args nil)) (handler-case (loop for i upfrom 0 do (push (sb-debug::arg i) args)) (sb-kernel::index-too-large-error () args))) :showvalue '|inspect input| :stream *trace-output*) ;; present return values :print-after (present-object sb-debug:*trace-values* :showvalue '|inspect return values| :stream *standard-output*) ;; passing other args to trace ,@rest)) Maybe an sbcl expert can really improve and beautify this hack. Sorry if mail is duplicated. -- Luigi Panzeri aka Matley Chiave pubblica su http://www.imati.cnr.it/~panzeri/matley.asc Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Evaluate Lisp: http://lisp.tech.coop/Evaluate%20Lisp

1 0

[slime-devel] Tracing with slime presentations
by Luigi Panzeri 09 Mar '06

09 Mar '06

Hi. i wrote a snippet to do tracing of functions using slime presentations (thanks to segv for showing me the slime presentation features and writing present-object) . Obviously this code works only on sbcl. (defun present-object (value &optional (stream *error-output*)) (swank::presenting-object value stream (prin1 value stream)) value) (defmacro slime-presentation-trace (fun) `(trace ,fun :print (present-object (let ((args nil)) (handler-case (loop for i upfrom 0 do (push (sb-debug::arg i) args)) (sb-kernel::index-too-large-error (var) args)))) :print-after (present-object sb-debug:*trace-values*))) Maybe an sbcl hacker can really improve and beautify this hack

1 0

[slime-devel] Problems with SLIME and SBCL
by Nicolas Neuss 08 Mar '06

08 Mar '06

Hello, since quite some time I am not able to run SLIME together with SBCL anymore. I did not care too much, since CMUCL and Allegro worked. However, I now am looking again at using OS threads on Linux/AMD64, and SBCL is my only option here. So I am interested to get it working again. Thus, I downloaded sbcl-0.9.9-x86-64-linux, CVS slime from today (Emacs on this machine is version 21.4.1), and did the usual installation as (add-to-list 'load-path PATH-TO-SLIME) (require 'slime) (slime-setup) Unfortunately, M-x slime does not succeed. The inferior-lisp buffer shows: WARNING: These Swank interfaces are unimplemented: (ACTIVATE-STEPPING CALLS-WHO DISASSEMBLE-FRAME INSPECT-FOR-EMACS SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN WHO-BINDS WHO-CALLS WHO-MACROEXPANDS WHO-REFERENCES WHO-SETS WHO-SPECIALIZES) T * ;; Swank started at port: 34981. NIL * Process inferior-lisp hangup Can anyone help me? Thank you very much, Nicolas.

2 2

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

08 Mar '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.852 slime/ChangeLog:1.853 --- slime/ChangeLog:1.852 Sat Mar 4 15:13:25 2006 +++ slime/ChangeLog Tue Mar 7 04:50:25 2006 @@ -1,3 +1,8 @@ +2006-03-06 Nathan Bird <nathan(a)acceleration.net> + + * slime.el: (slime-create-filename-translator): use the tramp + methods for dissecting and building filenames. + 2006-03-04 Wojciech Kaczmarek <wojtekk(a)kofeina.net> * slime.el (slime-filename-translations): Typo in example.

1 0

[slime-devel] Code Snippets for Debugging
by Gregory Novak 07 Mar '06

07 Mar '06

Attached are two code snippets that I came up with since I started using slime a few weeks ago. Probably there exist better ways to do these things, but I couldn't find them so I wrote my own. If there really isn't an existing way to do these things, perhaps they could be added to Slime. The first is intended to facilitate debugging. Often I find myself in an sldb buffer looking at a stack trace and it's not clear what went wrong. I'd like to evaluate some expressions in the stack frame to see intermediate results, but I don't want to type them in again. After all, I already typed them in and they're sitting there in the source file. So I type "v" in the debug buffer, put the point in an interesting place and execute gsn/slime-eval-last-expression-in-frame. It finds the sexp at point, switches to the sldb buffer, evaluates the expression, and then switches back. One sub-optimal thing is that the frame in which the expression is evaluated depends on hte position of the point in the sldb buffer even though you use the command in your source buffer. But using sldb-show-source, this seems to work fairly well. The second set of functions is alters slime-next-note/slime-previous-note to scan through certain types of compiler notes, rather than hitting them all. I found that I was getting zillions of notes and the errors were getting lost in the mix. So gsn/slime-next-not and gsn/slime-previous-note by default scan through all notes. However, with a prefix arg, they prompt for a type of error and henceforth stop only at that type of note. Comments/suggestions on style/implementation are welcome. Greg ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (defun gsn/slime-eval-last-expression-in-frame (sexp) "Eval the expression at POINT in a frame in the slime debugger. The frame used is determined by the location of POINT in the slime debugger buffer. The idea is to be able to be able to debug by using sldb-show-source in the slime debug buffer and then easily evaluate expression in your source file near the problem." (interactive (list (slime-last-expression))) (if (not (sldb-get-default-buffer)) (error "No debugger buffer") (save-excursion (set-buffer (sldb-get-default-buffer)) (sldb-eval-in-frame sexp)))) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (defvar gsn/slime-scan-note-by-type-history nil "List storing history of entries to minibuffer prompt in gsn/slime-read-type") (defvar gsn/slime-scan-note-by-type-current '(:error :read-error :warning :style-warning :note) "Current type of note for which to search. This is stored so that the behavior is 'sticky' between invocations of the commands.") (defun gsn/slime-next-note (reset-type) "Interactively search for the next compiler note of the type given by gsn/slime-scan-note-by-type-current. With prefix arg, prompt for the value of gsn/slime-scan-note-by-type-current." (interactive "P") (when reset-type (gsn/slime-read-type)) (gsn/slime-next-note-by-type gsn/slime-scan-note-by-type-current)) (defun gsn/slime-previous-note (reset-type) "Interactively search for the previous compiler note of the type given by gsn/slime-scan-note-by-type-current. With prefix arg, prompt for the value of gsn/slime-scan-note-by-type-current." (interactive "P") (when reset-type (gsn/slime-read-type)) (gsn/slime-previous-note-by-type gsn/slime-scan-note-by-type-current)) (defun gsn/slime-read-type () "Prompt for the value of gsn/slime-scan-note-by-type-current. Store history (as strings) in gsn/slime-scan-note-by-type-history. Convert the string to a symbol and set gsn/slime-scan-note-by-type-current." (let ((type-string (completing-read "Type (default error): " '("all" "error" "read-error" "warning" "style-warning" "note") nil t nil 'gsn/slime-scan-note-by-type-history "error"))) (push type-string gsn/slime-scan-note-by-type-history) (setq gsn/slime-scan-note-by-type-current (cdr (assoc type-string '(("all" . (:error :read-error :warning :style-warning :note)) ("error" . (:error)) ("read-error" . (:read-error)) ("warning" . (:warning)) ("style-warning" . (:style-warning)) ("note" . (:note)))))))) (defun gsn/slime-scan-note-by-type (type scan-func) "Move point to the next/previous compiler note of type TYPE. SCAN-FUNC specifies how to advance through the notes so that this function doens't have to be duplicated for -next- and -previous-" (let ((original-pos (point)) (last-pos (point)) (sought-note-p (lambda (type) (and (slime-note-at-point) (memq (overlay-get (slime-note-at-point) 'severity) type))))) (funcall scan-func) (while (and (/= last-pos (point)) (not (funcall sought-note-p type))) (setq last-pos (point)) (funcall scan-func)) ;; let the user know if there are no more notes (if (funcall sought-note-p type) (slime-show-note (slime-note-at-point)) ;; If no next note, go back to where you started (goto-char original-pos) (message "No more notes.")))) (defun gsn/slime-next-note-by-type (type) "Move point to the next compiler note of type TYPE." (gsn/slime-scan-note-by-type type 'slime-find-next-note)) (defun gsn/slime-previous-note-by-type (type) "Move point to the next/previous compiler note of type TYPE." (gsn/slime-scan-note-by-type type 'slime-find-previous-note)) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

1 0

[slime-devel] hacking "modern mode" in Franz
by Christopher C.Stacy 07 Mar '06

07 Mar '06

I frobbed this in swank-loader.lisp: ;======================================================================== (defun lisp-case-mode () #-allegro :case-insensitive #+allegro excl:*current-case-mode*) (defun unique-directory-name () "Return a name that can be used as a directory name that is unique to a Lisp implementation, Lisp implementation version, operating system, and hardware architecture." (flet ((first-of (features) (loop for f in features when (find f *features*) return it)) (maybe-warn (value fstring &rest args) (cond (value) (t (apply #'warn fstring args) "unknown")))) (let ((lisp (maybe-warn (first-of *implementation-features*) "No implementation feature found in ~a." *implementation-features*)) (os (maybe-warn (first-of *os-features*) "No os feature found in ~a." *os-features*)) (arch (maybe-warn (first-of *architecture-features*) "No architecture feature found in ~a." *architecture-features*)) (version (maybe-warn (lisp-version-string) "Don't know how to get Lisp ~ implementation version.")) (case (maybe-warn (lisp-case-mode) "Don't know uppercase/lowercase mode."))) (format nil "~(~@{~a~^-~}~)" lisp version case os arch)))) ;========================================================================

1 0

[slime-devel] slime-create-filename-translator revisted.
by Nathan Bird 07 Mar '06

07 Mar '06

I really liked the new slime translation stuff that went in a few days ago... except that tramp is a little bit different on xemacs. Part of it though, tramp has lots of functions for manipulating filenames. If we are going to depend on tramp for this feature, the automatic creation of translation functions, then lets use the tramp stuff that already has this configuration and functions built in. Here is a lisp paste showing what can be done with the new configuration. http://paste.lisp.org/display/17592 If you like, I can go link this from Cliki as well. Nathan Bird nathan(a)acceleration.net ? foo.el ? swank-loader.fas ? swank-loader.lib Index: ChangeLog =================================================================== RCS file: /project/slime/cvsroot/slime/ChangeLog,v retrieving revision 1.852 diff -u -r1.852 ChangeLog --- ChangeLog 4 Mar 2006 20:13:25 -0000 1.852 +++ ChangeLog 7 Mar 2006 04:46:46 -0000 @@ -1,3 +1,8 @@ +2006-03-06 Nathan Bird <nathan(a)acceleration.net> + + * slime.el: (slime-create-filename-translator): use the tramp + methods for dissecting and building filenames. + 2006-03-04 Wojciech Kaczmarek <wojtekk(a)kofeina.net> * slime.el (slime-filename-translations): Typo in example. Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.593 diff -u -r1.593 slime.el --- slime.el 4 Mar 2006 20:13:51 -0000 1.593 +++ slime.el 7 Mar 2006 04:46:49 -0000 @@ -1285,7 +1285,7 @@ remote-host username) "Creates a three element list suitable for push'ing onto -slime-filename-translations which uses tramp to load files on +slime-filename-translations which uses Tramp to load files on hostname using username. MACHINE-INSTANCE is a required parameter, REMOTE-HOST defaults to MACHINE-INSTANCE and USERNAME defaults to (user-login-name). @@ -1294,23 +1294,20 @@ which is just the value returned by cl:machine-instance on the remote lisp. REMOTE-HOST is the fully qualified domain name (or just the IP) of the remote machine. USERNAME is the username we -sholud login with." - (setf remote-host (or remote-host machine-instance) - username (or username (user-login-name))) - (lexical-let ((tramp-prefix (concat "/ssh:" username "@" remote-host ":"))) +should login with. +The functions created here expect your tramp-default-method or + tramp-default-method-alist to be setup correctly." + (lexical-let ((remote-host (or remote-host machine-instance)) + (username (or username (user-login-name)))) (list (concat "^" machine-instance "$") - `(lambda (emacs-filename) - (subseq emacs-filename (length ,tramp-prefix))) + (lambda (emacs-filename) + (tramp-file-name-localname + (tramp-dissect-file-name emacs-filename))) `(lambda (lisp-filename) - (concat ,tramp-prefix lisp-filename))))) - -(defun* slime-add-filename-translation (&key machine-instance - remote-host - username) - (push (slime-create-filename-translator :machine-instance machine-instance - :remote-host remote-host - :username username) - slime-filename-translations)) + (tramp-make-tramp-file-name nil + ,username + ,remote-host + lisp-filename))))) ;;;; Starting SLIME

2 3

[slime-devel] SLIME+Allegro on Windows
by mikel 06 Mar '06

06 Mar '06

Franz wants Peter Seibel's Lispbox to work with acl on Windows. The obstacle is that acl is not a console application on Windows, and doesn't provide a connection to standard input and standard output in the normal way. I've agreed to do a little legwork to find a way around this problem, and the first thing it occurred to me to do was to ask SLIME-devel what sort of connection support SLIME would need to connect to acl. Is it sufficient for the running acl to provide sockets, so that the lisp-side server can respond to the emacs-side SLIME protocol? What issues am I not thinking of in my naive view of this problem?

10 11

[slime-devel] Error signalling and handling in DEFINTERFACE methods?
by Peter Seibel 05 Mar '06

05 Mar '06

After being bit for about the billionth time by trying to ,cd to a file rather than a directory with the result of leaving *default-pathname-defaults* set to something that doesn't merge will with others, I decided to see if I could make SLIME protect me from myself. As a quick proof of concept, I made this change to swank-allegro.lisp: Index: swank-allegro.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-allegro.lisp,v retrieving revision 1.82 diff -u -r1.82 swank-allegro.lisp --- swank-allegro.lisp 10 Feb 2006 16:54:01 -0000 1.82 +++ swank-allegro.lisp 5 Mar 2006 18:09:36 -0000 @@ -85,6 +85,8 @@ "allegro") (defimplementation set-default-directory (directory) + (unless (excl:probe-directory directory) + (break "~a not a directory." directory)) (let ((dir (namestring (setf *default-pathname-defaults* (truename (merge-pathnames directory)))))) (excl:chdir dir) @@ -500,7 +502,7 @@ (defmethod inspect-for-emacs ((o standard-object) (inspector acl-inspector)) inspector - (values (format "~A is a standard-object." o) (allegro-inspect o))) + (values (format nil "~A is a standard-object." o) (allegro-inspect o))) (defun allegro-inspect (o) (loop for (d dd) on (inspect::inspect-ctl o) (Hmmm, the last chunk of that patch looks like some minor bug fix that I've had lying around that could usefully be applied to the mainline.) But that raises two questions: 1) Is there a standard protocol for signalling errors from functions that are invoked via comma shortcuts? At the moment simply BREAKing does the trick in the sense that I can then abort out of the debugger with no harm done but it seems a bit gross. 2) Is there some clever way to provide a *partial* default implementation. That is, I'd like in swank-backend.lisp to do the error checking (using a suitably portable replacement for EXCL:PROBE-DIRECTORY) before doing the moral equivalent of a CALL-NEXT-METHOD to get to the implementation-specific version. A literal CALL-NEXT-METHOD won't work, it seems, since although DEFIMPLEMENTATION expands to a method, it always expands to a method with default (i.e. T) specializations on all its parameters. -Peter -- Peter Seibel * peter(a)gigamonkeys.com Gigamonkeys Consulting * http://www.gigamonkeys.com/ Practical Common Lisp * http://www.gigamonkeys.com/book/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel March 2006