slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] allegro inspect typo
by Gábor Melis 16 Mar '06

16 Mar '06

Index: swank-allegro.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-allegro.lisp,v retrieving revision 1.83 diff -u -p -r1.83 swank-allegro.lisp --- swank-allegro.lisp 14 Mar 2006 04:30:14 -0000 1.83 +++ swank-allegro.lisp 16 Mar 2006 16:14:32 -0000 @@ -510,7 +510,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)

2 1

[slime-devel] Error using ,cd (~ not expanded)
by Stefan Kamphausen 16 Mar '06

16 Mar '06

Hi, since a few days I have this problem: * Open XEmacs * Start SLIME (M-x slime) * Wait for CMUCL to come up * Type ,cd [RET] * Select a directory, say ~/src/lisp/my-current-project [RET] * Get an error: File-error in function LISP::%SET-DEFAULT-DIRECTORY: "~/src/lisp/my-current-project" doesn't exist. [Condition of type KERNEL:SIMPLE-FILE-ERROR] Restarts: 0: [ABORT-REQUEST] Abort handling SLIME request. 1: [ABORT] Return to Top-Level. Backtrace: 0: (LISP::%SET-DEFAULT-DIRECTORY "~/src/lisp/my-current-project") 1: ((METHOD SWANK-BACKEND:SET-DEFAULT-DIRECTORY NIL (T)) #<#1=unused-arg> #<#1#> "~/src/lisp/my-current-project") 2: ("DEFUN EVAL-FOR-EMACS") 3: ((METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK NIL (T T)) #<#1=unused-arg> #<#1#> #<Function SWANK:SWANK-DEBUGGER-HOOK {5879B171}> #<Closure Over Function "DEFUN EVAL-FOR-EMACS" {58B14A91}>) 4: ("DEFUN HANDLE-REQUEST") I think it boils down to the ~ not being expanded. When I... * ... first use M-x cd to change to the dir and then accept the default in ,cd it works. * ... give the full path like /home/user/src/lisp/my-current-project it works. I can try to track this down if you give me any pointers what to look for, but maybe someone here more familiar with the code just sees the solution immediately? My System: * SLIME CVS HEAD * XEmacs 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid * CMUCL CMU Common Lisp CVS 19c 19c-release + minimal debian patches (19C) * Gentoo Linux Regards, Stefan -- "Feel free" mit GMX FreeMail! Monat f�r Monat 10 FreeSMS inklusive! http://www.gmx.net

2 2

[slime-devel] [patch] closing connections with :fd-handler style
by Stephen Compall 15 Mar '06

15 Mar '06

As far as I can tell, the only way a Swank connection object with style :fd-handler will ever be closed due to EOF (with close-connection) is if either the fd-handler implementation detects the EOF state and knows how to destroy Swank connections, or a condition is raised in the dynamic context of with-reader-error-handler. Looking at the topmost form in that context, however, it can only happen if (listen socket) answers T, so that the attempt to read can proceed and raise an eof-error, which gets wrapped up, etc. I modified process-available-input to test (listen socket) only after calling FN at least once; after all, it always returns T when the handler is called for a normal input state. Without this patch, my fd-handler backend gets into an endless loop calling the handler in install-fd-handler (with the :eof state); with this patch, the socket is closed, removed from *connections*, and from the fd-handler backend properly. Attached is the patch. -- Stephen Compall http://scompall.nocandysoftware.com/blog

2 4

[slime-devel] Odd bug - heads up
by Alan Ruttenberg 15 Mar '06

15 Mar '06

I found that presentations which were in my repl input history, weren't being recalled as presentations when I recalled previous history - they were coming back as text, and so would generally trigger a reader error when I tried the command. I tracked this down to (defun slime-repl-replace-input (string) (slime-repl-delete-current-input) (setq it string) (insert-and-inherit string)) If one uses insert, instead of insert-and-inherit then repl history works correctly for presentations, for me. No idea why this is problematic. It looks like this function has been this way for a long time - perhaps a bug in the emacs I am using (OS X tiger, fink installed, I think). Anyways, thought I'd post this in case anyone else was having the same problem, or had some insight as to why this is happening. -Alan

2 1

[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 07 Mar '06

07 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel