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

[slime-devel] Re: Serverside Sources
by Dr. Helmut G. Enders 29 Jul '08

29 Jul '08

> Helmut Eller wrote: > >> I'm looking for a solution, to keep the source files >> locally, on my laptop (near my emacs). > > If you just need a webserver on the remote machine, I would recommend to > install a webserver on the laptop and to develop most of the time on the > laptop only. One of our application coordinates different stocks of a company. It is a nearly 1 G Image and we have to change things remote. Slime works like a charm!!! Requests from users can be solved within Minutes. > Put the source files under something like CVS and use that > for synchronization. and Michael Weber wrote: > GNU Emacs also has something called "File Shadowing" which could be used: > http://www.gnu.org/software/emacs/manual/html_node/emacs/File-Shadowing.html Thanks, I haven't known that. > Instead of slime-compile-file you could use slime-compile-region (on the > entire buffer). This doesn't copy the file to the remote machine but > M-. etc. should work as long as the buffer exists. > > If you don't mind to change SLIME, you could create a command which > copies the file, either with scp or via SLIME's connection, before > calling slime-compile-file. Additionally you can set > slime-from-lisp-filename-function and slime-to-lisp-filename-function so > that the Lisp side loads the remote copy but reports compiler messages > etc. on the local file. > > If the filename translation functions are setup properly, the following > should work: > > > (defun my-compile-file () > (interactive) > (slime-eval `(swank:overwrite-file > ,(slime-to-lisp-filename (buffer-file-name)) > ,(buffer-substring-no-properties (point-min) (point-max)))) > (slime-compile-and-load-file)) > > > > (swank::defslimefun swank::overwrite-file (filename string) > (with-open-file (stream filename :direction :output > :if-exists :supersede > :if-does-not-exist :create) > (write-sequence string stream) > (finish-output stream)) > t) > Thanks, that's :-) nearly :-) what I want. (slime-compile-and-load-file) calls (swank:compile-file-for-emacs.. and then (compile-file ... on the swank side. The HSpec says that the input-file parameter of the 'compile-file' - function is a 'pathname designator' and this can be "a stream associated with a file.." Can I, within swank, fetch the file from the emacs side, e.g. with scp and give that stream as the input-file parameter to compile-file... Do you think it's work a try, or is it more 'not worth a straw', (...then lisp doesn't know the source place of the function, does it?) > > Helmut. ditto.

2 1

[slime-devel] What happens when net connection broken
by Roman Budzianowski 29 Jul '08

29 Jul '08

What is the currently implemented behavior of the remote stream in swank when the net connection breaks? I started a long running function and at some point the network went down. The remote lisp is still running and I managed to reconnect through tty because it was running in "screen". I am trying to restart the swank server. I am just wondering if swank thread is still running or is blocked on output. Is there a way to reconnect, like in 'screen. This is in allegro CL. Roman

2 3

[slime-devel] Output lost after disconnect reconnect
by Gábor Melis 29 Jul '08

29 Jul '08

After a disconnect, reconnect long running worker threads that were spawn for instance by C-x C-e in a lisp buffer send their output to the void. Detailed process to reproduce: 1. start an sbcl 2. (require 'asdf) (asdf:oos 'asdf:load-op 'swank) (setq swank:*globally-redirect-io* t) (setq swank:*global-debugger* t) (setf swank:*use-dedicated-output-stream* nil) (swank:create-server :dont-close t :port 4007) 3. connect from slime 4. from a buffer eval (loop (sleep 5) (print 'hello *trace-output*) (force-output *trace-output*)) 5. disconnect [At this point output should be going to the terminal where sbcl was started which is the case when the above snippet is wrapped in (sb-thread:make-thread (lambda () ...))). Instead it goes to nowhere.] 6. slime-connect again 7. observe that nobody says hello anymore The attached patch aims to fix this by: * swank.lisp (maybe-call-with-io-redirection): don't CALL-WITH-REDIRECTED-IO if *GLOBALLY-REDIRECT-IO*. Fixes lost output after disconnect, reconnect. Cheers, Gábor Melis

2 5

[slime-devel] Serverside Sources
by Dr. Helmut G. Enders 29 Jul '08

29 Jul '08

Hi, I'm using slime to connect to sbcl on a remote server. It works faultless and I'm very happy with it. My only problem is that I also have to keep the source files on the remote server. With trampoline this is no problem, too. I'm looking for a solution, to keep the source files locally, on my laptop (near my emacs). I tried sshfs, and nfs, scp etc., but this is very clumsy, if you use a laptop and access the server from different locations. (Different versions locally and on the server, etc.) Do you see a chance that after ^c-^k th remote lisp requests the source file via the slime protocol from my local laptop. So I would have all the sources of my projects, which run on different remote servers, locally on my laptop, save, always uptodate, easy for version management etc. Helmut

3 2

[slime-devel] [PATCH] Supplying environment variables to Lisp
by Richard M Kreuter 29 Jul '08

29 Jul '08

Hi, I'd like to propose the following feature, implemented in the attached patch: to allow slime-lisp-implementations to specify a list of strings to augment the process environment of the Lisp process. I've a couple of uses for this feature: (1) to run SLIME out of an SBCL build directory, with an implementation specification like this: (sbcl-cvs ("/home/me/sbcl-cvs/src/runtime/sbcl" "--core" "/home/me/sbcl-cvs/output/sbcl.core") :program-environment ("SBCL_HOME=/home/me/sbcl-cvs/contrib/")) (2) to work with Lisp applications that need environment variables during initialization, which variables I don't want to set Emacs-wide (because they might leak into unrelated things I do in other buffers, etc): (myworld-v1 ("/path/to/myworld-v1/bin/myworld") :program-environment ("LD_LIBRARY_PATH="/path/to/myworld-v1/lib/") (myworld-v2 ("/path/to/myworld-v2/bin/myworld") :program-environment ("LD_LIBRARY_PATH="/path/to/myworld-v2/lib/")) I know these things can already be done with wrapper scripts (and they still can), but I find wrapper scripts less pleasant to maintain than my .emacs file. The patch has been tested under GNU Emacs CVS and Xemacs 21.4. If the feature is okay but the implementation needs work in order to be merged, please let me know. Thanks, RmK

2 1

[slime-devel] [PATCH] *globally-redirect-io* and *communication-style* troubles
by Richard M Kreuter 29 Jul '08

29 Jul '08

Hi, When I run SBCL under slime with *GLOBALLY-REDIRECT-IO* true and *COMMUNICATION-STYLE* :FD-HANDLER or :SIGIO, I get a repl buffer with name "*slime-repl nil*", and any subsequent SBCLs created by slime steal this buffer. The problem is that with *GLOBALLY-REDIRECT-IO*, the initial "Adding ... handler" messages get to Emacs before the reply to (swank:connection-info), and so the event processing on the slime side creates the repl buffer before the slime connection has been initialized. Getting rid of those messages seems to fix things. Thanks, RmK --- swank-sbcl.lisp 17 Jul 2008 22:19:11 -0000 1.199 +++ swank-sbcl.lisp 22 Jul 2008 22:22:39 -0000 @@ -133,7 +133,6 @@ (defimplementation add-sigio-handler (socket fn) (set-sigio-handler) (let ((fd (socket-fd socket))) - (format *debug-io* "Adding sigio handler: ~S ~%" fd) (enable-sigio-on-fd fd) (push (cons fd fn) *sigio-handlers*))) @@ -146,7 +145,6 @@ (defimplementation add-fd-handler (socket fn) (declare (type function fn)) (let ((fd (socket-fd socket))) - (format *debug-io* "; Adding fd handler: ~S ~%" fd) (sb-sys:add-fd-handler fd :input (lambda (_) _ (funcall fn)))))

2 1

[slime-devel] [PATCH] slime-quit-lisp from a non-default connection
by Richard M Kreuter 29 Jul '08

29 Jul '08

Hi, slime-quit-lisp gets an error in slime-connection when quitting from a slime-repl buffer associated with a connection other than the default. To reproduce: (1) make one slime connection, (2) make another slime connection, (3) switch to the first connection's slime-repl buffer, (4) use ,q<RET>. The error isn't terribly serious, but it leaves *inferior-lisp* buffers behind, which can be annoying in some modes of usage. I think the trouble is that slime-quit-lisp is killing something too early, but I'm not certain. Whatever the cause, the attached patch seems to make the error go away, at least for my setup. Thanks, RmK

2 1

[slime-devel] ,quit with multiple connections
by Stas Boukarev 28 Jul '08

28 Jul '08

When I have multiple connections and do ,quit in the non-default repl i get: "Lisp connection closed unexpectedly: connection broken by remote peer" and default repl becomes unusable but its inferior process works. If I do this in default repl everything's fine. -- With Best Regards, Stas.

2 1

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

27 Jul '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1374 slime/ChangeLog:1.1375 --- slime/ChangeLog:1.1374 Wed Jul 23 10:29:26 2008 +++ slime/ChangeLog Sat Jul 26 19:05:59 2008 @@ -1,3 +1,14 @@ +2008-07-27 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank.lisp (swank-compiler): Fix bug when invoking an abort + restart on a failed compilation attempt. + + * swank-sbcl.lisp (swank-compile-string): If a compilation attempt + fails, COMPILE-FILE returns NIL which we tried to LOAD. Fix that. + + * swank-backend.lisp (swank-compile-string, swank-compile-file): + Document return value. + 2008-07-23 Tobias C. Rittweiler <tcr(a)freebits.de> * swank-loader.lisp (*contribs*): Added `swank-package-fu'.

1 0

[slime-devel] second slime does not use lisp process arguments
by Antony Sequeira 25 Jul '08

25 Jul '08

Hi I am using slime from cvs (I think downloaded around July 5th) In my .emacs i put (setq slime-default-lisp 'sbcl) (setq slime-lisp-implementations '( (sbcl ("sbcl" "--userinit" "/home/antony/fooo.lisp") :coding-system utf-8-unix ) (ccl ("/home/antony/bin/ccl")) )) I run M-x slime and it starts sbcl correctly If I change (setq slime-default-lisp 'sbcl) to (setq slime-default-lisp 'ccl) Now ccl runs correctly , but when I do C-u M-x slime sbcl it runs sbcl but does not seem to use the parameters "sbcl" "--userinit" "/home/antony/fooo.lisp The same thing thing happens vice versa for ccl (which I don't understand at all since it has no parameters, I have it hard coded in my shell script home/antony/bin/ccl) Summary of the problem as I see it - I can't have a second slime that uses program arguments I can include more of my .emacs if this is not sufficient. Thanks, -Antony

2 1