slime-devel March 2004

slime-devel@common-lisp.net

30 participants
71 discussions

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

04 Mar '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.277 slime/ChangeLog:1.279 --- slime/ChangeLog:1.277 Wed Mar 3 02:34:35 2004 +++ slime/ChangeLog Wed Mar 3 15:57:46 2004 @@ -1,5 +1,23 @@ 2004-03-03 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + * swank.lisp: Use *emacs-connection*, *active-threads*, and + *thread-counter* as thread local dynamic variables. + (init-emacs-connection): Don't set *emacs-connection*. + (create-connection, dispatch-event): Pass the connection object to + newly created threads. + (with-connection): New macro + (handle-request, install-fd-handler, debug-thread): Use it. + + * swank-allegro.lisp, swank-clisp.lisp, swank-cmucl.lisp, + swank-openmcl.lisp, swank-sbcl.lisp (call-with-compilation-hooks): + Bind fewer variables. Most of them are already bound in + swank.lisp. + + * swank.lisp (setup-server, serve-connection): New dont-close + argument to keep the socket open after the first connection. + (start-server, create-swank-server): Update callers. + Reported by Bill Clementson. + * swank-cmucl.lisp (resolve-note-location): Don't be too clever, if there is no context available. The compiler notes buffer is probably more adequate in this situation. @@ -18,8 +36,8 @@ * swank.lisp (find-completions): Deleted. (simple-completions): Use longest-common-prefix instead of longest-completion. - (inspect-in-frame): Moved here from swank-cmucl.lisp. - + (inspect-in-frame): Moved here from swank-cmucl.lisp. + * swank-lispworks.lisp (call-with-debugging-environment): Bind *sldb-top-frame*. (nth-frame): Use *sldb-top-frame*.

1 0

[slime-devel] Improvement of compilation buffer
by Ivan Boldyrev 04 Mar '04

04 Mar '04

I like when compilation buffer appear after compilation only when it is not empty. Very simple patch is below: :) -- Ivan Boldyrev Sorry my terrible English, my native language is Lisp!

2 2

[slime-devel] Sometimes function arglists stop displaying
by Peter Seibel 03 Mar '04

03 Mar '04

I've noticed this a few times: I'll be using SLIME and suddenly space no longer causes the function arglists to show up in the minibuffer. SPC is still bound to slime-space but it doesn't work in either Lisp source code buffers or REPL buffers. I certainly didn't do anything on purpose to turn it off. I just observed it in Allegro though since I switch impls a lot I'm not sure if that's the only place I've seen it. I'll try to look into it if I get a chance but I thought I post here in case anyone else knows anything about it. -Peter -- Peter Seibel peter(a)javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp

2 1

Re: [slime-devel] Using SLIME with ACL on Win2000
by Bill_Clementson＠peoplesoft.com 03 Mar '04

03 Mar '04

Helmut Eller <e9626484(a)stud3.tuwien.ac.at> writes: > Bill_Clementson(a)peoplesoft.com writes: > > [snip] > > I have another question: > > I see that you can create multiple SLIME repl's to the same lisp by just > > manually connecting on different sockets. However, if I open 2 connections, > > all output (whether from repl[1] or repl[2] goes to repl[2]. Presumably > > both repl's are using *standard-output* and this is why the output from > > both goes to the same emacs buffer. Is this a bug or is there a specific > > command that I should be using for creating a second repl or is there > > something that needs to be specified manually so that output from each repl > > is directed to the correct buffer? A side effect of this is that once you > > evaluate something in repl[1] and the output is sent to repl[2], the prompt > > disappears from repl[1]. You can still enter expressions and evaluate them; > > however, you no longer have the prompt. > > This wasn't supported. There were some global variables and creating > a second socket overwrote the current state, so that all requests were > effectively handled by the second connection. I reorganized some > things a bit and the variables in question are now thread local. It > should now work to create multiple servers in the same Lisp. That fixes it - thanks! - Bill

1 0

Re: [slime-devel] Using SLIME with ACL on Win2000
by Bill_Clementson＠peoplesoft.com 03 Mar '04

03 Mar '04

Helmut Eller <e9626484(a)stud3.tuwien.ac.at> writes: > Bill_Clementson(a)peoplesoft.com writes: > > > I've just recently tried out SLIME on Windows and think it's really neat. > > (I posted a comment on my weblog a few days ago at: > > http://home.comcast.net/~bc19191/blog/040229.html ) > > Thank you for the kind words in the article. We should probably make > a link from our Cliki pages. That's fine with me. > [snip] > > > (load "c:/usr/home/site/slime/swank-loader.lisp") > > (swank::create-swank-server 4005) > > > > Is this typical or is there some better approach? > > The normal way to start Lisp is M-x slime. Is there a reason you > can't use that? The lisp executable needs to be a WIN32 console application in order to be launched from an Emacs inferior lisp process. The ACL Trial edition executables under MS Windows are WIN32 Windows applications and can not be launched from an inferior lisp in Emacs. Franz also ship a build.exe with their regular product (but not the trial edition) - this is a WIN32 console application but there are issues with multiprocessing support with this executable and it is really only shipped (IMO) for legacy support reasons. Therefore, regardless of whether you use the ACL trial or the ACL commercial product under Windows, it is preferable to use the Windows application version of the executable. That is why I manually launch alisp.exe and load the .slime.lisp file to start up swank. > [snip] > > > Is there some alternative way to connect to an already started lisp process > > or am I just doing something wrong? > > We used to close the server socket when the connection was > established. The latest version has a DONT-CLOSE argument and you > should now be able to reconnect if you start it with: > > (swank:create-swank-server 4005 :spawn #'swank::simple-announce-function t) > > [I will probably switch to keyword arguments in the future or add a > new function] Neat - my version of SLIME was ancient (3 days :-) old) so I didn't have that functionality. However, I've downloaded the latest CVS version and it works perfectly! > And in case it wasn't obvious, there should never be a need to > disconnect. That would be is a bug and I'd like hear about it. If I have a long-running process, it is nice to be able to exit Emacs and re-connect to a running lisp. I have another question: I see that you can create multiple SLIME repl's to the same lisp by just manually connecting on different sockets. However, if I open 2 connections, all output (whether from repl[1] or repl[2] goes to repl[2]. Presumably both repl's are using *standard-output* and this is why the output from both goes to the same emacs buffer. Is this a bug or is there a specific command that I should be using for creating a second repl or is there something that needs to be specified manually so that output from each repl is directed to the correct buffer? A side effect of this is that once you evaluate something in repl[1] and the output is sent to repl[2], the prompt disappears from repl[1]. You can still enter expressions and evaluate them; however, you no longer have the prompt. - Bill

2 1

Re: [slime-devel] Sometimes function arglists stop displaying
by Bill_Clementson＠peoplesoft.com 03 Mar '04

03 Mar '04

Peter Seibel <peter(a)javamonkey.com> writes: > I've noticed this a few times: I'll be using SLIME and suddenly space > no longer causes the function arglists to show up in the minibuffer. > SPC is still bound to slime-space but it doesn't work in either Lisp > source code buffers or REPL buffers. I certainly didn't do anything on > purpose to turn it off. I just observed it in Allegro though since I > switch impls a lot I'm not sure if that's the only place I've seen it. > I'll try to look into it if I get a chance but I thought I post here > in case anyone else knows anything about it. I haven't noticed that with Allegro/SLIME under w2k. When it happens, did you try pressing "C-h k SPC" to see whether space was still bound to slime-space? Perhaps some other emacs code is re-defining the space key. If it is still bound, did you try debugging slime-space and slime-arglist in emacs? - Bill

1 0

[slime-devel] Using SLIME with ACL on Win2000
by Bill_Clementson＠peoplesoft.com 03 Mar '04

03 Mar '04

I've just recently tried out SLIME on Windows and think it's really neat. (I posted a comment on my weblog a few days ago at: http://home.comcast.net/~bc19191/blog/040229.html ) I initially played around with CLISP and SLIME but have recently started using SLIME with ACL under W2K. I'm impressed by how much functionality you guys have delivered in the last few months. I have 2 questions: 1. How do most people who are using ACL with Windows connect? I have the following in my .emacs file so that I kick off ACL and start SLIME by pressing "F5": (global-set-key [(f5)] '(lambda () (interactive) (shell-command "c:/bin/acl-6.2/alisp.exe +B +cm -L ~/.slime.lisp&") (delete-other-windows) (slime-connect "localhost" 4005))) (the slime.lisp file that I load automatically has the following 2 lines in it: (load "c:/usr/home/site/slime/swank-loader.lisp") (swank::create-swank-server 4005) Is this typical or is there some better approach? 2. When I kill SLIME in Emacs (but don't kill the ACL process), I thought that I would be able to re-connect to the ACL process by just running slime-connect again. However, this doesn't work. The message I get in Emacs (regardless of whether I answer the "close network connection" message with yes or no) is: "open-network-stream: make client process failed: connection refused, :name, SLIME Lisp, :buffer, nil, :host, localhost, :service, 4005" The ACL listener shows the following: ;; Connection to Emacs lost. ; Fast loading c:\bin\acl-6.2\code\acldns.005 ;;; Installing acldns patch, version 5 ;; [eof encountered on stream #<MULTIVALENT stream socket connected from localhost/4005 to localhost/2303 @ #x204df1a2>] Is there some alternative way to connect to an already started lisp process or am I just doing something wrong? Thanks, Bill Clementson

2 1

[slime-devel] Interactive compile loses DSPEC info
by Alain.Picard＠memetrics.com 03 Mar '04

03 Mar '04

Another one: I'm using latest CVS slime + Lispworks on Linux. If I compile and load my system from scratch, I can use M-. to jump around function definitions. but if I go to a function, hit C-c C-c to recompile the function, jump to a different emacs buffer and try M-. on the newly compiled function, I now get: make-single-line (:error The file #P"/tmp/filecLlfIH.lisp" does not exist.) (:location (:file /home/kooks/XOS/Bullseye/src/Common/generic-utilities.lisp) (:function-name MAKE-SINGLE-LINE)) in the *XREF buffer. Cheers,

3 7

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 03 Mar '04

03 Mar '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.276 slime/ChangeLog:1.277 --- slime/ChangeLog:1.276 Mon Mar 1 10:46:27 2004 +++ slime/ChangeLog Wed Mar 3 02:34:35 2004 @@ -1,3 +1,38 @@ +2004-03-03 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * swank-cmucl.lisp (resolve-note-location): Don't be too clever, + if there is no context available. The compiler notes buffer is + probably more adequate in this situation. + (compile-file-for-emacs): Use the :load argument to compile-file. + (inspect-in-frame): Deleted. + + * slime.el (slime-compilation-finished-hook): Use + slime-maybe-list-compiler-notes as default. + (slime-maybe-list-compiler-notes): New function. + (slime-list-compiler-notes): Insert "[no notes]" if there aren't + any. Pop to the buffer. + (slime-complete-symbol*, slime-simple-complete-symbol): Set the + lisp-mode-syntax-table in the completion buffer. + (check-parens): Compatibility function for XEmacs and Emacs 20. + + * swank.lisp (find-completions): Deleted. + (simple-completions): Use longest-common-prefix instead of + longest-completion. + (inspect-in-frame): Moved here from swank-cmucl.lisp. + + * swank-lispworks.lisp (call-with-debugging-environment): Bind + *sldb-top-frame*. + (nth-frame): Use *sldb-top-frame*. + (name-source-location, name-source-locations): Renamed from + dspec-source-location, dspec-source-locations. The result now + includes methods for generic functions. + (eval-in-frame, return-from-frame, restart-frame): Implemented. + (compile-string-for-emacs): Set dspec::*location* to the buffer + location. + (signal-undefined-functions, signal-error-data-base) + (make-dspec-location): Remove temp-file kludges. + (patch-source-locations, replace-source-file): Deleted. + 2004-03-01 Marco Baringer <mb(a)bese.it> * swank.lisp (format-arglist): deal with nil arglists.

1 0

[slime-devel] Daily ChangeLog diff
by Luke Gorrie 02 Mar '04

02 Mar '04

Index: slime/ChangeLog diff -u slime/ChangeLog:1.274 slime/ChangeLog:1.276 --- slime/ChangeLog:1.274 Sun Feb 29 04:07:07 2004 +++ slime/ChangeLog Mon Mar 1 10:46:27 2004 @@ -1,3 +1,21 @@ +2004-03-01 Marco Baringer <mb(a)bese.it> + + * swank.lisp (format-arglist): deal with nil arglists. + +2004-03-01 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> + + * swank-lispworks.lisp (compile-string-for-emacs): Patch the + recorded source locations. + (replace-source-file, patch-source-locations): New function. + (dspec-buffer-position): Handle defgeneric. + (make-dspec-location): Handle (patched) emacs-buffer locations. + (emacs-buffer-location-p): New function. + (describe-primitive-type, inspected-parts): Implemented. + (kill-thread): Implemented. + + * swank-sbcl.lisp, swank-cmucl.lisp, swank-allegro.lisp + (kill-thread): Implemented. + 2004-02-29 Helmut Eller <e9626484(a)stud3.tuwien.ac.at> * slime.el (slime-complete-symbol): Make slime-complete-symbol

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 2004