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

[slime-devel] slime apparently mis-reporting closed connection
by Samium Gromoff 26 Oct '07

26 Oct '07

After well into the second decade of slime-disconnect/slime-connect loop iteration (interweaved with normal operation) the emacs side of slime stopped recognising connection status. I`m doing a slime-disconnect, restarting swank and slime-connect, however immediately after this either a slime-load-file or a (load ...) in slime repl result in a message "Connection closed." i have some time before i will have to reboot the machine, and until then i can provide various forensics upon request... regards, Samium Gromoff

5 5

[slime-devel] slime-apropos-package now sorts correctly
by Hoehle, Joerg-Cyril 20 Apr '07

20 Apr '07

Hi, slime-apropos-package now conforms to its specification and also sorts symbols printed with package prefix. I supply the patches as attachments in the hope that MS-Windows nor MS-Outlook will break the TAB and LF characters of the original diff. I hope this is fine. Regards, Jörg Höhle.

3 3

[slime-devel] slime-display-edit-hilights
by Marco Baringer 23 Dec '06

23 Dec '06

for those of you who don't follow c.l.l (which is probaly a good idea) i commited William Bland's patch[1]. see the ChangeLog for details. 1 - http://groups.google.com/group/comp.lang.lisp/browse_thread/thread/e1d0b7bf… -- -Marco Ring the bells that still can ring. Forget the perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen

8 20

[slime-devel] OpenGL Integration into the REPL ?
by Sean Charles 14 Dec '06

14 Dec '06

Hello, I am currently developing 'something interesting' using SBCL and OpenGL via Apple X11. I have built SBCL and OpenGLUT from source as I am lucky enough to have an Intel 20" iMac and I wanted to make sure I was getting maximum speed i.e. no Rosetta in the way. My 'project' is coming along but it bugs me that I have to keep stopping and starting the application in order to make changes to the software because once the 'glutMainLoop' gets control the SLIME session doesn't respond anymore. I had to slightly modify the cl-opengl package as it has two symbol naming problems concerning the roman fonts but that is the only change I have had to make along with the library.lisp package which needed to be coaxed into loading my OpenGLUT build on an Intel Darwin platform. Apart from that it works very well, the MESADEMOS:GEARS averages about 4900 frames per second much to my disbelief!!! I know that SBCL does not currently support threading on the intel iMac which maybe would solve all my problems in one fell swoop. Software: SLIME CVS latest as of 13-July-2006 SBCL 0.9.13 OpenGLUT 0.6.3 I have spent a few hours reading the SWANK code trying to see where I can make changes but I am just to new to it, I have used SLIME but never before had a need to modify it and right now it looks a bit intimidating to try and figure out how to do what I would like to do which is basically find a way to make the OpenGL timer function and the display function both to 'keep the SWANK backend alive' by somehow calling whatever is needed to ensure that the SLIME session remains active at the same time as my OpenGL application is running. For me this would be incredibly productive as it means (if I have understood LISP so far [used Smalltalk for about 6 years]) that I can fiddle with my application while it is running and see any changes that affect the display be effected the next time the display is rendered. Is this at all possible??? I would think that a new SWANK back end could be created. I have also toyed with the idea of hacking the SBCL source code directly to contain the OpenGL libraries and somehow making the changes at that point but id I thought SWANK / SLIME was big, SBCL is enormous by comparison and I'd rather be coding my application that fiddling with the tools. Many thanks Sean Charles www.objitsu.com

5 6

[slime-devel] How to inspect locals
by Jonathon McKitrick 27 Aug '06

27 Aug '06

Hi all, when running SBCL and a condition occurs that causes a break, how can I view the locals that have been bound in the function? Viewing the arguments isn't hard, but I cannot seem to figure out the locals. -Jonathon -- "I am sure that Jesus would use a command prompt. Hello? Ten Commandments??"

12 17

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

29 Jul '06

Index: slime/ChangeLog diff -u slime/ChangeLog:1.922 slime/ChangeLog:1.923 --- slime/ChangeLog:1.922 Mon Jul 24 10:01:22 2006 +++ slime/ChangeLog Fri Jul 28 11:05:52 2006 @@ -1,3 +1,13 @@ +2006-07-28 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-thread-quit): Call swank:quit-thread-browser. + Reported by Taylor R Campbell. + +2006-07-28 Willem Broekema <metawilm(a)gmail.com> + + * swank-allegro.lisp: Profiling functions on Allegro (except for + profile-package). + 2006-07-24 Matthias Koeppe <mkoeppe(a)mail.math.uni-magdeburg.de> Add support for destructuring macro arglists in arglist display, @@ -68,6 +78,7 @@ * swank.lisp (keywords-of-operator): New support function for writing user-defined `extra-keywords' methods. +>>>>>>> 1.922 2006-07-11 Helmut Eller <heller(a)common-lisp.net> * swank-allegro.lisp (make-weak-key-hash-table): Use ACL's weak

1 0

[slime-devel] editing files on local swank and remote swank
by Rüdiger Sonderfeld 28 Jul '06

28 Jul '06

Hello, I want to run a swank server on a remote machine and on my local machine. I configured slime according to http://paste.lisp.org/display/17592 and it works fine to edit remote files via tramp and compile them with swank. But I can't edit or compile local files anymore. I always get the following error message "Not a tramp file name: ..." How can I configure slime so that I can run local as well as on a remote machine and edit local and remote files? Thank you. Regards, Rüdiger Sonderfeld

3 2

[slime-devel] reporting SLIME errors from Lisp
by Taylor R Campbell 28 Jul '06

28 Jul '06

What's the best way to report errors in SLIME that were detected on the Lisp side, such as `no package FOO'? Right now in SLIME48 I just abort the RPC and log a message to the console about the error, but this is suboptimal, because all the user sees is `Evaluation aborted' or `Synchronous Lisp Evaluation aborted.' Perhaps :ABORT responses to RPCs could include optional error messages?

2 1

[slime-devel] Problems with swank and Allegro CL
by Damien Kick 28 Jul '06

28 Jul '06

I apologize if this is a duplicate. Perhaps I mistyped my e-mail address on a previous attempt to post. I am trying to load swank from Allegro CL and it is causing serious problems. CG-USER(1): (load (make-pathname :device "D" :directory '(:absolute "local" "share" "xemacs" "xemacs-packages" "snapshot" "slime") :name "swank" :type "asd")) ; Loading D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank.asd T CG-USER(2): (asdf:oos 'asdf:load-op :swank) ; Fast loading D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-loader.fasl Warning: *SOURCE-DIRECTORY*, :VARIABLE was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank.asd and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-loader.lisp ; Fast loading H:\.slime\fasl\2006-07-16\allegro-a7.0-mswindows-x86\swank-backend.fasl ; Fast loading H:\.slime\fasl\2006-07-16\allegro-a7.0-mswindows-x86\nregex.fasl ; Fast loading H:\.slime\fasl\2006-07-16\allegro-a7.0-mswindows-x86\swank-allegro.fasl Warning: (METHOD PREFERRED-COMMUNICATION-STYLE NIL), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD FORMAT-SLDB-CONDITION (T)), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD CONDITION-REFERENCES (T)), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD CALL-WITH-SYNTAX-HOOKS (T)), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD CALL-WITHOUT-INTERRUPTS (T)), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD LISP-IMPLEMENTATION-TYPE-NAME NIL), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD SET-DEFAULT-DIRECTORY (T)), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD DEFAULT-DIRECTORY NIL), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD ARGLIST (T)), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD MAKE-STREAM-INTERACTIVE (T)), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD INITIALIZE-MULTIPROCESSING NIL), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD THREAD-NAME (T)), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD THREAD-STATUS (T)), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD MAKE-LOCK NIL), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD CALL-WITH-LOCK-HELD (T T)), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD CURRENT-THREAD NIL), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD KILL-THREAD (T)), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD MAKE-WEAK-KEY-HASH-TABLE NIL), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp Warning: (METHOD MAKE-WEAK-VALUE-HASH-TABLE NIL), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-backend.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp ; Fast loading H:\.slime\fasl\2006-07-16\allegro-a7.0-mswindows-x86\swank-gray.fasl ; Autoloading for class FUNDAMENTAL-CHARACTER-OUTPUT-STREAM: ; Fast loading from bundle code\STREAMC.fasl. ; Fast loading from bundle code\efft-1252-base.fasl. ; Fast loading from bundle code\efft-utf8-base.fasl. ; Fast loading from bundle code\efft-void.fasl. ; Fast loading from bundle code\efft-latin1-base.fasl. ; Fast loading H:\.slime\fasl\2006-07-16\allegro-a7.0-mswindows-x86\swank.fasl Warning: (METHOD INSPECT-FOR-EMACS #'T), :OPERATOR was defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank-allegro.lisp and is now being defined in D:\local\share\xemacs\xemacs-packages\snapshot\slime\swank.lisp Warning: These Swank interfaces are unimplemented: (ACTIVATE-STEPPING ADD-FD-HANDLER ADD-SIGIO-HANDLER INSPECT-FOR-EMACS PROFILE PROFILE-PACKAGE PROFILE-RESET PROFILED-FUNCTIONS REMOVE-FD-HANDLERS REMOVE-SIGIO-HANDLERS SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN UNPROFILE WHO-SPECIALIZES) NIL Error: Bad type of object (SYNONYM-STREAM) passed to parent. The object was #<SYNONYM-STREAM @ #x20c60aca>. [Current process: Listener 1] CG-USER(3): nil Error: Bad type of object (SYNONYM-STREAM) passed to parent. The object was #<SYNONYM-STREAM @ #x20c60aca>. [Current process: Listener 1] CG-USER(3): I'm using the following versions. CG-USER(1): (lisp-implementation-type) "International Allegro CL Trial Edition" CG-USER(2): (lisp-implementation-version) "7.0 [Windows] (Jul 21, 2006 17:02)" CG-USER(3): (software-type) "Microsoft Windows 98/Me and 2000/XP/Server 2003" CG-USER(4): (software-version) "Generic" CG-USER(5):

2 3

[slime-devel] bug in quitting thread browser?
by Taylor R Campbell 28 Jul '06

28 Jul '06

Emacs's `slime-thread-quit' omits the SWANK:QUIT-THREAD-BROWSER RPC. I assume that the existence of the function on the Lisp side implies that it's meant to be called; is this a bug?

2 1