slime-devel October 2007

slime-devel@common-lisp.net

21 participants
29 discussions

[slime-devel] inspect-slot-for-emacs (without html)
by Knut Olav Bøhmer 10 Oct '07

10 Oct '07

(Forgot, to remove html in mail...) How about doing something like this in inspect-slot-for-emacs file: cvs/slime/contrib/swank-fancy-inspector.lisp function: inspect-slot-for-emacs (eval (read-from-string value-string)))))))) + (:action ,(custom-inspect-name class object slot) + ,(lambda () (custom-inspect-call class object slot))) ,@(when boundp `(" " (:action "[make unbound]" With the following methods something like this: (defmethod custom-inspect-name (class object slot) "[No custom inspections]") (defmethod custom-inspect-call (class object slot) nil) And then one could make own methods specializing on your own classes and slots. (defmethod custom-inspect-name ((class person) object (slot company)) (format nil "[boss of ~a]" (name-of person)) (defmethod custom-inspect-call ((class person) object (slot company)) (slime-inspect (boss-of person)) Or whatever object models you have. Maybe make custom-inspect-call to follow relations in cl-sql.... (and add necessary checks, restarts and handler-cases) -- Free Software Consultant Cell: +47 - 47 34 40 08 Phone: +47 - 21 53 69 00, Fax: +47 - 21 53 69 09 Addr: Slemdalsveien 70, PB 1 Vinderen, 0319 Oslo

1 0

[slime-devel] weird ^D errors
by Cyrus Harmon 06 Oct '07

06 Oct '07

ok, for some weeks now, I've been getting this sporadic error where I start navigating through a file and I get errors such as this: unknown &KEY argument: :|PRI^DNT-RIGHT-MARGIN| obviously, the ^D in the middle of print-right-margin isn't right. But it's not just print-right-margin, yet it always seems to be a ^D. Has anyone else seen such a problem? I'm running on a threaded version of SBCL (1.0.10.29) for MacOS with a reasonably recent carbon emacs built from CVS (current head doesn't run, but that's another story; perhaps emacs is the culprit here). Thanks, Cyrus

1 0

[slime-devel] Status of ECL support
by Ralf Mattes 05 Oct '07

05 Oct '07

Hello list, I'm trying to use Slime (CVS/HEAD) with ECL but run into the following error: ralf@mhflaptop01:/LISP/slime$ rlwrap ecl ;;; Loading #P"/usr/lib/ecl/cmp.fas" ;;; Loading #P"/usr/lib/ecl/sysfun.lsp" ECL (Embeddable Common-Lisp) 0.9i Copyright (C) 1984 Taiichi Yuasa and Masami Hagiya Copyright (C) 1993 Giuseppe Attardi Copyright (C) 2000 Juan J. Garcia-Ripoll ECL is free software, and you are welcome to redistribute it under certain conditions; see file 'Copyright' for details. Type :h for Help. Top level. > (load "swank-loader.lisp") ;;; Loading "/LISP/slime/swank-loader.lisp" LAMBDA: Too many arguments to function COMPILE-FILES-IF-NEEDED-SERIALLY. Broken at EVAL.No restarts available. Broken at COMPILE-FILES-IF-NEEDED-SERIALLY. SWANK-LOADER>> (Same error when run from within emacs btw). Is this a known problem? Cheers, Ralf Mattes

1 0

[slime-devel] slime-inspect doesn't work on presentations any more
by Stelian Ionescu 03 Oct '07

03 Oct '07

The attached patch makes SLIME-INSPECT work on presentations again. The code is a cleanup of the first half of slime-inspect before the split. -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.

2 2

[slime-devel] Strange behaviour by slime-selector
by massali＠stud.ntnu.no 03 Oct '07

03 Oct '07

I'm using Emacs 22.1 and CVS version of slime. Strange behaviour: After I open a .lisp file in lisp-mode I start slime. Then the window splits. I get my source file on the top and repl at the bottom. Now, if I am in the repl, and use the slime selector to my source file, I get "Can't find unshown buffer in lisp-mode" However, if I close the frame(C-x 5 0) with my source code and then try to use the slime selector to my source file, it works. Kjeld.

2 1

[slime-devel] OpenMCL inspector patch
by R. Matthew Emerson 03 Oct '07

03 Oct '07

In swank-openmcl.lisp, there's a function called CLOSURE-CLOSED-OVER- VALUES. For about a year now, OpenMCL has included CCL::CLOSURE-CLOSED-OVER- VALUES, which produces results in the expected format, and should probably be used instead. It correctly displays the closed-over values on x86-64 OpenMCL---the function in swank-openmcl.lisp doesn't. Alternatively, (ccl::%svref closure (+ 1 (- howmany n))) could be replaced with (ccl::nth-immediate closure (+ 1 (- howmany n))) NTH-IMMEDIATE has been around for over 2 years, and I would hope that nobody is running an OpenMCL older than that...

1 0

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 02 Oct '07

02 Oct '07

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.60 slime/contrib/ChangeLog:1.62 --- slime/contrib/ChangeLog:1.60 Sun Sep 30 18:41:56 2007 +++ slime/contrib/ChangeLog Mon Oct 1 09:37:22 2007 @@ -1,3 +1,18 @@ +2007-10-01 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime-autdoc.el (slime-autodoc-message-ok-p): Don't display an + arglist when the minibuffer is active. + +2007-10-01 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime-typeout-frame.el: Messages in the typeout frame were too + easily overwritten by `slime-autodoc'. Fix that. + Reported by Geoff Wozniak. + + (slime-typeout-message-aux): Split out from `slime-typeout-message'. + (slime-typeout-message): Wrapper around it. Additionally disable + the autodoc timer temporarily. + 2007-09-30 Geoff Wozniak <geoff(a)wozniak.ca> * slime-typeout-frame.el (slime-typeout-frame-init): Fix quoted

1 0

[slime-devel] Typeout frame, autodoc-mode and notes
by Geoff Wozniak 01 Oct '07

01 Oct '07

When using the typeout frame with slime-autodoc-mode enabled, reading notes using slime-next-note and slime-previous-note is difficult. This is due to the fact that slime-autodoc-pre-command-refresh-echo- area is on pre-command-hook and wipes the echo area clean right after the note is displayed. I've attached a patch to remedy this for the time being, but it feels very unclean. All I did was adjust the conditions in slime-autodoc- message-ok-p such that it returns nil when last-command is eq to either slime-next-note or slime-previous-note. This at least lets you read the note before you start to adjust the code (once you do anything else, the echo area is wiped clean). This behaviour is suitable to me for the time being, which is why I'm submitting a patch. I'm not sure if something else should done about this, such as making notes appear for a fixed period of time in a typeout frame or something like that. -- Geoff

2 1

[slime-devel] Daily ChangeLog diff
by mbaringer＠common-lisp.net 01 Oct '07

01 Oct '07

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.59 slime/contrib/ChangeLog:1.60 --- slime/contrib/ChangeLog:1.59 Fri Sep 28 09:06:30 2007 +++ slime/contrib/ChangeLog Sun Sep 30 18:41:56 2007 @@ -1,3 +1,8 @@ +2007-09-30 Geoff Wozniak <geoff(a)wozniak.ca> + + * slime-typeout-frame.el (slime-typeout-frame-init): Fix quoted + FUNCTION forms in literal. + 2007-09-28 Tobias C. Rittweiler <tcr(a)freebits.de> * README: Updated.

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 October 2007