- slime-devel - mailman3.common-lisp.net

[slime-devel] Is there an easy way to open an output stream in lisp that goes to a slime buffer?
by Peter Seibel 17 Sep '04

17 Sep '04

Clearly there's some machinery in SLIME for creating streams that are actually connected to sockets that communicate with emacs. My question is there an easy way to, on the Common Lisp side, open a stream such that a new buffer is created in emacs and all data sent to the stream will end up in that buffer? I.e. I'm hoping to be able to do something like this: (format (make-slime-stream) "hello, world!~%") and have "hello, world!" appear in a new emacs buffer. (Actually what I'm really hoping to do is redirect the log of AllegroServe to a slime buffer so it's easy to get at without it cluttering up either the SLIME REPL or *inferior-lisp*. -Peter -- Peter Seibel peter(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

2 1

[slime-devel] more inspector updates (possible breakage)
by marco 17 Sep '04

17 Sep '04

the inspector now shows the specializer-direct-methods of a class and can deal with eql-specializers in methods. as usual i commited changes for lispworks and allegro without testing, if someone would mind updating to the latest slime and telling me if things break. thanks. p.s. - i'm done with the inspector (except for bug fixes) if someone is looking for a small slime project integrating the inspector and xref would be pretty cool. hint. hint. hint. -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

2 1

[slime-devel] inspector for clisp
by marco 17 Sep '04

17 Sep '04

i just commited an implementation of the inspector for clisp. however it only runs on the CVS version of clisp (the one which has a complete MOP). how important is it that slime runs on clisp 2.33? -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

4 9

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 16 Sep '04

16 Sep '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.533 slime/ChangeLog:1.536 --- slime/ChangeLog:1.533 Wed Sep 15 21:00:15 2004 +++ slime/ChangeLog Thu Sep 16 17:58:52 2004 @@ -1,3 +1,16 @@ +2004-09-16 Marco Baringer <mb(a)bese.it> + + * swank-clisp.lisp (swank-mop, inspect-for-emacs): Only define the + CLOS parts of the inspector if the underlying lisp provides the + required functionality. If not enough MOP is present to implement + the inspector then we define some very simple replacement methods. + +2004-09-16 Marco Baringer <mb(a)bese.it> + + * swank-clisp.lisp (swank-mop): Implement the MOP compatability + package. + (inspect-for-emacs): Update for new inspection API. + 2004-09-15 Alan Ruttenberg <alanr-l(a)mumble.net> * swank-openmcl: typo in who-references. Fix frame-var-value

1 0

[slime-devel] the inspector (warning allegro and lispworks users)
by marco 16 Sep '04

16 Sep '04

i just changed the swank inspector api. inspect-for-emacs (ex inspected-parts) now takes a second argument which is an inspector object. this means that we get implementation specific inspectors where available and default generic inspectors otherwise and clears up the load order issues i was having. i went and re-wrote all the implementation inspector methods to use the new return-value format (previously those methods were being ignored so the issue never came up). HOWEVER: I also made these changes for allegro and lispworks, even though i don't have neither an allegro nor a lispworks to test the changes on. i may very well have b0rken things. -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

5 7

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

15 Sep '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.528 slime/ChangeLog:1.533 --- slime/ChangeLog:1.528 Tue Sep 14 23:35:13 2004 +++ slime/ChangeLog Wed Sep 15 21:00:15 2004 @@ -1,3 +1,33 @@ +2004-09-15 Alan Ruttenberg <alanr-l(a)mumble.net> + * swank-openmcl: typo in who-references. Fix frame-var-value + +2004-09-15 Marco Baringer <mb(a)bese.it> + + * slime.el (slime-inspector-label-face, + slime-inspector-value-face, slime-inspector-action-face, + slime-inspector-type-face): These faces now inherit from similar + font-lock-<whatever> faces. + (slime-open-inspector): Use slime-inspector-value-face for values. + + * swank.lisp (inspect-for-emacs): Add function and compiler-macro + documentation when inspecting symbols. View the truename of + logical pathnames where they exist. Fix typos in package + inspector (fix by Torsten Poulin <torsten(a)diku.dk>). + + * swank-sbcl.lisp, swank-cmucl.lisp (inspect-for-emacs): Insert + function object's documentation when it's available. + +2004-09-15 Eduardo Muñoz <emufer(a)terra.es> + + * .cvsignore: Added *.elc + + * hyperspec.el: Fixed syntax error. + +2004-09-15 Alan Caulkins <fatman(a)maxint.net> + + * swank.lisp (cleanp-connection-threads): Kill all Swank threads + for a connection when it terminates. + 2004-09-14 Thomas Schilling <tjs_ng(a)yahoo.de> * swank-allegro.lisp (inspect-for-emacs): Fixes to previous patch.

1 0

[slime-devel] define-minor-mode autoload problem
by Reini Urban 15 Sep '04

15 Sep '04

(require 'slime) error message: "Autoloading failed to define define-minor-mode" I needed this change on xemacs win32 native, because define-minor-mode is already fboundp: autoloaded. (eval-and-compile (require 'cl) (require 'easy-mmode) ;(unless (fboundp 'define-minor-mode) (defalias 'define-minor-mode 'easy-mmode-define-minor-mode));) (May be a FAQ) How to detect in elisp if the function is autoloaded? I this is bogus I have to do (require 'easy-mmode) (defalias 'define-minor-mode 'easy-mmode-define-minor-mode) in my .emacs -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/

2 1

[slime-devel] couple minor patches
by Eduardo Muñoz 15 Sep '04

15 Sep '04

Inlined below Index: .cvsignore =================================================================== RCS file: /project/slime/cvsroot/slime/.cvsignore,v retrieving revision 1.2 diff -u -r1.2 .cvsignore --- .cvsignore 18 Oct 2003 05:07:49 -0000 1.2 +++ .cvsignore 13 Sep 2004 20:27:54 -0000 @@ -1,3 +1,4 @@ *.x86f *.fasl -*.dfsl \ No newline at end of file +*.dfsl +*.elc Index: hyperspec.el =================================================================== RCS file: /project/slime/cvsroot/slime/hyperspec.el,v retrieving revision 1.6 diff -u -r1.6 hyperspec.el --- hyperspec.el 3 Jul 2004 00:06:30 -0000 1.6 +++ hyperspec.el 13 Sep 2004 20:33:50 -0000 @@ -1113,7 +1113,7 @@ ;;; FORMAT character lookup by Frode Vatvedt Fjeld <frodef(a)acm.org> 20030902 ;;; -:;; adjusted for ILISP by Nikodemus Siivola 20030903 +;;; adjusted for ILISP by Nikodemus Siivola 20030903 (defvar common-lisp-hyperspec-format-history nil "History of format characters looked up in the Common Lisp HyperSpec.") -- Eduardo Muñoz | (prog () 10 (print "Hello world!") http://213.97.131.125/ | 20 (go 10))

2 1

[slime-devel] SBCL, multiple (zombie?) processes problems
by rif 15 Sep '04

15 Sep '04

I'm finding that if I try to run SLIME with SBCL on my debian machine, that multiple sbcl processes (4) start, and if I immediately type (quit) at the REPL, only one of the four is killed. If I instead go into *inferior-lisp* and type (quit), it quit's out of all 4. If I quit the REPL one first, then go to *inferior-lisp*, I get errors like "interrupt thread 6376 failed (3: No such process). This seems to indicate to me some bad interaction between SBCL threads/processes and SLIME? I wouldn't care that much about the zombies, but my XML-RPC server is also not working in SLIME (calls to it hang forever, works fine if I start sbcl in a shell), and I suspect the difficulties are related. Any thoughts? This seems to be an issue with both the current SLIME (CVS today) and the 1.0 tarball (I tried switching to the 1.0 tarball by deleting both the old SLIME directory and my .slime directory --- is anything else necessary)? Cheers, rif

6 13

[slime-devel] MOP problem with clisp
by Reini Urban 14 Sep '04

14 Sep '04

cygwin clisp - slime CVS HEAD: (load "swank-loader.lisp") ... FIND-CLASS: SWANK-MOP:STANDARD-SLOT-DEFINITION does not name a class :q The following functions were used but not defined: SWANK-MOP:GENERIC-FUNCTION-LAMBDA-LIST SWANK-MOP:GENERIC-FUNCTION-METHOD-CLASS SWANK-MOP:GENERIC-FUNCTION-METHOD-COMBINATION SWANK-MOP:GENERIC-FUNCTION-METHODS SWANK-MOP:GENERIC-FUNCTION-NAME SWANK-MOP:METHOD-GENERIC-FUNCTION SWANK-MOP:METHOD-LAMBDA-LIST SWANK-MOP:METHOD-SPECIALIZERS SWANK-MOP:METHOD-QUALIFIERS SWANK-MOP:CLASS-DIRECT-SUPERCLASSES SWANK-MOP:CLASS-DIRECT-SLOTS SWANK-MOP:CLASS-SLOTS SWANK-MOP:CLASS-DIRECT-SUBCLASSES SWANK-MOP:CLASS-PRECEDENCE-LIST SWANK-MOP:CLASS-FINALIZED-P SWANK-MOP:CLASS-PROTOTYPE SWANK-MOP:SLOT-DEFINITION-NAME SWANK-MOP:SLOT-DEFINITION-DOCUMENTATION SWANK-MOP:SLOT-DEFINITION-INITARGS SWANK-MOP:SLOT-DEFINITION-INITFORM SWANK-MOP:SLOT-DEFINITION-INITFUNCTION The following special variables were not defined: SWANK-BACKEND::CODE The following special variables were defined too late: SWANK-BACKEND::*BUFFER-NAME* SWANK-BACKEND::*BUFFER-OFFSET* The following functions were used but are deprecated: SET 0 errors, 9 warnings earlier slime's didn't have this problem. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/

3 4