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

[slime-devel] clhs-lookup for reader macros
by Stas Boukarev 27 Feb '09

27 Feb '09

I added reader macros for hyperspec-lookup, hope this would be useful. -- With Best Regards, Stas.

2 1

[slime-devel] Saving *slime-scratch*
by Nikodemus Siivola 11 Oct '08

11 Oct '08

The attached patch associates *slime-scratch* with a file if you name one as "slime-scratch-file". I've been running slime with this a while, and rather like it. Something like this was talked about a while ago, and dropped because of what looked like an ideologinal objection to scratch-buffers in my mind. Is the consensus still against this? Cheers, -- Nikodemus Index: slime.el =================================================================== RCS file: /project/slime/cvsroot/slime/slime.el,v retrieving revision 1.784 diff -u -r1.784 slime.el --- slime.el 16 Apr 2007 14:42:33 -0000 1.784 +++ slime.el 27 Apr 2007 13:26:17 -0000 @@ -4570,10 +4570,15 @@ (set-keymap-parent map lisp-mode-map) map)) +(defvar slime-scratch-file nil) + (defun slime-scratch-buffer () "Return the scratch buffer, create it if necessary." (or (get-buffer "*slime-scratch*") - (with-current-buffer (get-buffer-create "*slime-scratch*") + (with-current-buffer (if (not slime-scratch-file) + (get-buffer-create "*slime-scratch*") + (find-file slime-scratch-file)) + (rename-buffer "*slime-scratch*") (lisp-mode) (use-local-map slime-scratch-mode-map) (slime-mode t)

4 5

[slime-devel] slime-c-p-c
by Madhu 08 Sep '08

08 Sep '08

Re: slime-complete-symbol* : I noticed that slime-c-p-c does not work correctly but can mangle text after a completion is chosen , [I'm appending a test case to the end of this message.] I'm afraid I'm to blame for this, I think: the patch I submitted claiming to fix XEmacs behaviour (on 2007-08-04) and which was committed on 2007-09-04 is incorrect [ 1. the analysis is not restricted to XEmacs, and 2. Emacs choose-completion does not work right unless the text in the buffer is a proper prefix of the completions displayed. I cannot see any lowest-common-denominator solution for this.] I would suggest reverting the patch. The downside is that you get back the original behaviour, which mangles the text BEFORE the completion is chosen: If you type "m-v" and hit TAB the function will delete your text and leave you with "m" -- because "m" is emacs' completed-prefix matching both "machine-version" and "multiple-value*"s. [This may or may not be acceptable, indeed whether it is what you want would depend on which buffer you are in, and what symbol you are trying to complete] Apologies for the incomplete patch and the earlier noise over the [unrelated yet related] unambiguous-prefix issue (from 06).. -- Madhu ;;; PS: Here is a test case transcript, and also what to expect on the ;;; suggest fix : ;;; ;;; 1. First we recreate the situation in acl, where there are multiple ;;; completions for "l-p-t". ;;; CL-USER> '(locale-print-time logical-pathname-translations logical-pathname-translations-database-pathnames) (LOCALE-PRINT-TIME LOGICAL-PATHNAME-TRANSLATIONS LOGICAL-PATHNAME-TRANSLATIONS-DATABASE-PATHNAMES) ;;; ;;; 2. slime-c-p-c-unambiguous-prefix-p is set to nil ;;; BEFORE: CL-USER> l-p-t ;;; ^^^ hit TAB, then choose the logical-pathname-translations ;;; completion in the *Completions* buffer ;;; AFTER: The completed form looks like: CL-USER> (l-plogical-pathname-translations ;;; ;;; 3. Next try after setting slime-c-p-c-unambiguous-prefix-p nil ;;; BEFORE: CL-USER> l-p-t ;;; ^^^ hit TAB, then choose the logical-pathname-translations ;;; completion in the *Completions* buffer ;;; AFTER: CL-USER> (logical-pathname-translationsp-t ;;; ;;; 4.WITH 2007-09-04 PATCH REVERTED: ;;; BEFORE: CL-USER> l-p-t ;;; ^^^ hit TAB, then choose the logical-pathname-translations ;;; completion in the *Completions* buffer ;;; AFTER: CL-USER> (lo ^^^ note that the text you input is gone. ;;; but at least choosing a completion won't mangle the text in your ;;; buffer

1 1

[slime-devel] [PATCH] fix the indentation of IF forms in the slime-indentation contrib
by Luis Oliveira 20 Aug '08

20 Aug '08

Hello, The attached patch changes the indentation of IF forms from (if foo bar baz) to (if foo bar baz) which is, AFAIK, the most widespread way of indenting IF forms. Also, this patch <http://common-lisp.net/~loliveira/patches/slime-changelog-nuke-trailing-whi…> removes lots of trailing whitespace from the ChangeLog via M-x delete-trailing-whitespace. -- Luís Oliveira http://student.dei.uc.pt/~lmoliv/

2 2

[slime-devel] Unicode support for CMUCL
by Raymond Toy 19 Aug '08

19 Aug '08

Here is a small patch to enable support for Unicode for CMUCL. Seems to work. May need some more work on the *external-format-to-coding-system*, but iso-8859-1 and utf-8 appear to work ok, for the little bit of testing I've done. Ray --- swank-cmucl.lisp-orig 2008-06-01 18:06:07.000000000 -0400 +++ swank-cmucl.lisp 2008-06-01 18:01:44.000000000 -0400 @@ -99,10 +99,13 @@ (ext:close-socket fd))) (defimplementation accept-connection (socket &key - external-format buffering timeout) - (declare (ignore timeout external-format)) + external-format buffering timeout) + (declare (ignore timeout)) (let ((buffering (or buffering :full))) - (make-socket-io-stream (ext:accept-tcp-connection socket) buffering))) + (make-socket-io-stream (ext:accept-tcp-connection socket) + buffering + :external-format + (or external-format :iso-8859-1)))) ;;;;; Sockets @@ -117,10 +120,23 @@ (let ((hostent (ext:lookup-host-entry hostname))) (car (ext:host-entry-addr-list hostent)))) -(defun make-socket-io-stream (fd buffering) +(defvar *external-format-to-coding-system* + '((:iso-8859-1 + "latin-1" "latin-1-unix" "iso-latin-1-unix" + "iso-8859-1" "iso-8859-1-unix") + (:utf-8 "utf-8" "utf-8-unix"))) + +(defimplementation find-external-format (coding-system) + (car (rassoc-if (lambda (x) (member coding-system x :test #'equal)) + *external-format-to-coding-system*))) + + +(defun make-socket-io-stream (fd buffering &key external-format) "Create a new input/output fd-stream for FD." (sys:make-fd-stream fd :input t :output t :element-type 'base-char - :buffering buffering)) + :buffering buffering + #+unicode :external-format + #+unicode external-format)) ;;;;; Signal-driven I/O

3 7

[slime-devel] Mercurial
by Helmut Eller 08 Aug '08

08 Aug '08

What do people think of switching from CVS to Mercurial[*] ? Helmut. [*] http://www.selenic.com/mercurial/

20 50

[slime-devel] step debugging in slime 3.0
by Andrew Gasparovic 30 Jul '08

30 Jul '08

Hello, Is there something special I have to do to turn on step debugging with sldb using slime 3.0 and sbcl 1.0.17 on OS X? When I type an 's' in an sldb buffer, I get "Evaluation aborted." in the minibuffer and execution continues. The sldb buffer itself goes blank but remains open. Thanks a lot! -Andrew

1 0

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

30 Jul '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1375 slime/ChangeLog:1.1378 --- slime/ChangeLog:1.1375 Sat Jul 26 19:05:59 2008 +++ slime/ChangeLog Tue Jul 29 07:03:31 2008 @@ -1,3 +1,24 @@ +2008-07-29 Richard M Kreuter <kreuter(a)progn.net> + + Environment variables for Lisp process. + + * slime.el (slime-start, slime-maybe-start-lisp) + (slime-reinitialize-inferior-lisp-p, slime-start-lisp) + (slime-restart-sentinel): Pass new parameter "env" through. + +2008-07-29 Richard M Kreuter <kreuter(a)progn.net> + + * swank-sbcl.lisp (add-sigio-handler, add-fd-handler): Be quiet + as a workaround for non-properly initialized *debug-io*. + +2008-07-29 Richard M Kreuter <kreuter(a)progn.net> + + Fix slime-quit-lisp in non-default REPL buffer. + + * slime.el (slime-quit-lisp): Killing the REPL buffer also removes + the buffer local binding of slime-buffer-connection. Remember the + connection before killing the buffer. + 2008-07-27 Tobias C. Rittweiler <tcr(a)freebits.de> * swank.lisp (swank-compiler): Fix bug when invoking an abort

1 0

[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

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

24 Jul '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1372 slime/ChangeLog:1.1374 --- slime/ChangeLog:1.1372 Sat Jul 19 07:34:19 2008 +++ slime/ChangeLog Wed Jul 23 10:29:26 2008 @@ -1,3 +1,13 @@ +2008-07-23 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank-loader.lisp (*contribs*): Added `swank-package-fu'. + +2008-07-23 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-at-list-p): New. Returns t if point is at a list. + (slime-at-expression-p): New. Similiar to `slime-in-expression-p'. + (slime-end-of-list): New. Pendant to `slime-beginning-of-list'. + 2008-07-19 Tobias C. Rittweiler <tcr(a)freebits.de> REPL shortcuts now leave an appropriate Common Lisp form in the Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.109 slime/contrib/ChangeLog:1.110 --- slime/contrib/ChangeLog:1.109 Sat Jul 19 07:39:23 2008 +++ slime/contrib/ChangeLog Wed Jul 23 10:27:36 2008 @@ -1,5 +1,12 @@ 2008-07-19 Tobias C. Rittweiler <tcr(a)freebits.de> + * slime-package-fu.el, swank-package-fu.lisp: New contrib to + aumatically add symbols to the relevant DEFPACKAGE forms. + You can use `C-c x' to export the symbol at point, and + `C-u C-c x' to unexport it. + +2008-07-19 Tobias C. Rittweiler <tcr(a)freebits.de> + * slime-asdf.el (slime-oos): Use `slime-repl-shortcut-async'. 2008-07-16 Tobias C. Rittweiler <tcr(a)freebits.de>

1 0

[slime-devel] No "Go to definition" with latest (CVS) slime and CLISP 2.46
by Blake McBride 21 Jul '08

21 Jul '08

Greetings, I just checked out the latest CVS slime and I am using it with CLISP 2.46. When I try Go to definition (M-.) I get: PARSE-NAMESTRING: argument #1=(SYSTEM::DEFUN/DEFMACRO #P"/home/blake/tmp/f1.fas" 6 7) should be a pathname designator #2=(OR STRING FILE-STREAM PATHNAME) [Condition of type SIMPLE-TYPE-ERROR] Restarts: 0: [ABORT] Return to SLIME's top level. 1: [CLOSE-CONNECTION] Close SLIME connection Backtrace: 0: [258] frame binding variables (~ = dynamically): | ~ SWANK::*SLDB-STEPPING-P* <--> NIL 1: [255] frame binding variables (~ = dynamically): | ~ SWANK::*SLDB-LEVEL* <--> 0 2: [252] frame binding variables (~ = dynamically): | ~ *PACKAGE* <--> #<PACKAGE COMMON-LISP-USER> 3: <1/246> #<COMPILED-FUNCTION SWANK::DEBUG-IN-EMACS> - #(NIL #<SIMPLE-TYPE-ERROR #x204027B6>) 4: <1/243> #<COMPILED-FUNCTION SWANK:SWANK-DEBUGGER-HOOK> [241] frame binding variables (~ = dynamically): | ~ *DEBUGGER-HOOK* <--> #<COMPILED-FUNCTION SWANK:SWANK-DEBUGGER-HOOK> 5: <1/238> #<SYSTEM-FUNCTION INVOKE-DEBUGGER> 1 [237] frame binding variables (~ = dynamically): | ~ SYSTEM::*PRIN-STREAM* <--> #<UNBOUND> 6: [234] frame binding variables (~ = dynamically): | ~ *PRINT-READABLY* <--> NIL 7: [231] frame binding variables (~ = dynamically): | ~ *PRINT-ESCAPE* <--> T 8: <1/228> #<SYSTEM-FUNCTION PARSE-NAMESTRING> 1 - #<UNBOUND> 9: <1/222> #<SYSTEM-FUNCTION PATHNAME-TYPE> - NIL 10: <1/217> #<COMPILED-FUNCTION SWANK-BACKEND::FSPEC-PATHNAME> - #<COMPILED-FUNCTION SWANK-BACKEND::FSPEC-LOCATION> 11: <1/215> #<COMPILED-FUNCTION SWANK-BACKEND::FSPEC-LOCATION> - FUN2 12: <1/212> #<COMPILED-FUNCTION #:|244 245 (DEFIMPLEMENTATION FIND-DEFINITIONS (NAME) ...)-21-1-1|> - #<COMPILED-FUNCTION #:|244 245 (DEFIMPLEMENTATION FIND-DEFINITIONS (NAME) ...)-21-1-1|> 13: <1/208> #<COMPILED-FUNCTION SWANK-BACKEND:FIND-DEFINITIONS> - #<COMPILED-FUNCTION SWANK::XREF>ELISP> 14: <1/202> #<COMPILED-FUNCTION SWANK:FIND-DEFINITIONS-FOR-EMACS> - #<COMPILED-FUNCTION SWANK:FIND-DEFINITIONS-FOR-EMACS> 15: [200] EVAL frame for form (SWANK:FIND-DEFINITIONS-FOR-EMACS "fun2") 16: [197] frame binding environments VAR_ENV <--> NIL FUN_ENV <--> NIL BLOCK_ENV <--> NIL GO_ENV <--> NIL DECL_ENV <--> ((DECLARATION OPTIMIZE DECLARATION)) 17: <1/192> #<SYSTEM-FUNCTION EVAL> [191] frame binding variables (~ = dynamically): | ~ SWANK::*BUFFER-PACKAGE* <--> #<UNBOUND> 18: [188] frame binding variables (~ = dynamically): | ~ SWANK::*PENDING-CONTINUATIONS* <--> NIL 19: [185] frame binding variables (~ = dynamically): | ~ SWANK::*BUFFER-READTABLE* <--> #<UNBOUND> 20: [181] unwind-protect frame 21: <1/176> #<COMPILED-FUNCTION SWANK::EVAL-FOR-EMACS-1> - #<COMPILED-FUNCTION SWANK::EVAL-FOR-EMACS-1> 22: [175] frame binding variables (~ = dynamically): | ~ *DEBUGGER-HOOK* <--> #<COMPILED-FUNCTION SWANK:SWANK-DEBUGGER-HOOK> 23: <1/171> #<COMPILED-FUNCTION #:|593 598 (DEFINTERFACE CALL-WITH-DEBUGGER-HOOK (HOOK FUN) ...)-57-3-1|> - #<COMPILED-FUNCTION #:|593 598 (DEFINTERFACE CALL-WITH-DEBUGGER-HOOK (HOOK FUN) ...)-57-3-1|> 24: <1/166> #<COMPILED-FUNCTION SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK> - #(NIL (SWANK:FIND-DEFINITIONS-FOR-EMACS "fun2") NIL 3) 25: <1/162> #<COMPILED-FUNCTION SWANK::EVAL-FOR-EMACS> <2/162> #<SYSTEM-FUNCTION FUNCALL> 4 - SWANK::EVAL-FOR-EMACS 26: <1/155> #<COMPILED-FUNCTION SWANK::READ-FROM-EMACS> [155] frame binding variables (~ = dynamically): | ~ SWANK::*SLDB-QUIT-RESTART* <--> ABORT 27: [152] frame binding variables (~ = dynamically): | ~ SYSTEM::*ACTIVE-RESTARTS* <--> (#S(RESTART :NAME SWANK::CLOSE-CONNECTION :TEST #1=#<COMPILED-FUNCTION SYSTEM::DEFAULT-RESTART-TEST> :INVOKE-TAG #:SIMPLE-RESTART-21493 :INVOKE-FUNCTION NIL :REPORT #<FUNCTION :LAMBDA (STREAM) (FORMAT STREAM "Close SLIME connection")> :INTERACTIVE #2=#<COMPILED-FUNCTION SYSTEM::DEFAULT-RESTART-INTERACTIVE> :MEANINGFULP T) #S(RESTART :NAME ABORT :TEST #1# :INVOKE-TAG NIL :INVOKE-FUNCTION #<COMPILED-FUNCTION SYSTEM::MAIN-LOOP-1-1> :REPORT #<COMPILED-FUNCTION SYSTEM::MAIN-LOOP-1-2> :INTERACTIVE #2# :MEANINGFULP T)) 28: [149] catch frame for tag #:SIMPLE-RESTART-20983 29: <1/145> #<COMPILED-FUNCTION SWANK::HANDLE-REQUEST-1> - #<COMPILED-FUNCTION SWANK::HANDLE-REQUEST-1> 30: [144] frame binding variables (~ = dynamically): | ~ *DEBUGGER-HOOK* <--> #<COMPILED-FUNCTION SWANK:SWANK-DEBUGGER-HOOK> 31: <1/140> #<COMPILED-FUNCTION #:|593 598 (DEFINTERFACE CALL-WITH-DEBUGGER-HOOK (HOOK FUN) ...)-57-3-1|> - #<COMPILED-FUNCTION #:|593 598 (DEFINTERFACE CALL-WITH-DEBUGGER-HOOK (HOOK FUN) ...)-57-3-1|> 32: <1/135> #<COMPILED-FUNCTION SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK> - #<COMPILED-FUNCTION SWANK::CALL-WITH-CONNECTION-1> 33: <1/132> #<COMPILED-FUNCTION SWANK::CALL-WITH-CONNECTION-1> - #<COMPILED-FUNCTION SWANK::CALL-WITH-CONNECTION-1> 34: [131] frame binding variables (~ = dynamically): | ~ *TERMINAL-IO* <--> #<IO TERMINAL-STREAM> 35: [128] frame binding variables (~ = dynamically): | ~ *STANDARD-INPUT* <--> #<IO SYNONYM-STREAM *TERMINAL-IO*> 36: [125] frame binding variables (~ = dynamically): | ~ *QUERY-IO* <--> #<IO SYNONYM-STREAM *TERMINAL-IO*> 37: [122] frame binding variables (~ = dynamically): | ~ *DEBUG-IO* <--> #<IO SYNONYM-STREAM *TERMINAL-IO*> 38: [119] frame binding variables (~ = dynamically): | ~ *TRACE-OUTPUT* <--> #<IO SYNONYM-STREAM *TERMINAL-IO*> 39: [116] frame binding variables (~ = dynamically): | ~ *ERROR-OUTPUT* <--> #<IO SYNONYM-STREAM *TERMINAL-IO*> 40: [113] frame binding variables (~ = dynamically): | ~ *STANDARD-OUTPUT* <--> #<IO SYNONYM-STREAM *TERMINAL-IO*> 41: <1/105> #<COMPILED-FUNCTION SWANK::CALL-WITH-REDIRECTED-IO> - #<COMPILED-FUNCTION SWANK::MAYBE-CALL-WITH-IO-REDIRECTION> 42: <1/102> #<COMPILED-FUNCTION SWANK::MAYBE-CALL-WITH-IO-REDIRECTION> [100] frame binding variables (~ = dynamically): | ~ SWANK::*EMACS-CONNECTION* <--> NIL 43: <1/95> #<COMPILED-FUNCTION SWANK::CALL-WITH-CONNECTION> [93] frame binding variables (~ = dynamically): | ~ SWANK::*SWANK-STATE-STACK* <--> NIL 44: <1/89> #<COMPILED-FUNCTION SWANK::HANDLE-REQUEST> - #<COMPILED-FUNCTION SWANK::SIMPLE-SERVE-REQUESTS-2> 45: <1/87> #<COMPILED-FUNCTION SWANK::SIMPLE-SERVE-REQUESTS-2> - #<COMPILED-FUNCTION SWANK::SIMPLE-SERVE-REQUESTS-2> 46: [86] handler frame for conditions SWANK::SWANK-ERROR 47: [80] compiled block frame for #S(RESTART :NAME SWANK::CLOSE-CONNECTION :TEST #<COMPILED-FUNCTION SYSTEM::DEFAULT-RESTART-TEST> :INVOKE-TAG #:SIMPLE-RESTART-21493 :INVOKE-FUNCTION NIL :REPORT #<FUNCTION :LAMBDA (STREAM) (FORMAT STREAM "Close SLIME connection")> :INTERACTIVE #<COMPILED-FUNCTION SYSTEM::DEFAULT-RESTART-INTERACTIVE> :MEANINGFULP T) 48: [76] frame binding variables (~ = dynamically): | ~ SYSTEM::*ACTIVE-RESTARTS* <--> (#S(RESTART :NAME ABORT :TEST #<COMPILED-FUNCTION SYSTEM::DEFAULT-RESTART-TEST> :INVOKE-TAG NIL :INVOKE-FUNCTION #<COMPILED-FUNCTION SYSTEM::MAIN-LOOP-1-1> :REPORT #<COMPILED-FUNCTION SYSTEM::MAIN-LOOP-1-2> :INTERACTIVE #<COMPILED-FUNCTION SYSTEM::DEFAULT-RESTART-INTERACTIVE> :MEANINGFULP T)) 49: [73] catch frame for tag #:SIMPLE-RESTART-21493 50: [70] unwind-protect frame 51: <1/66> #<COMPILED-FUNCTION SWANK::SIMPLE-SERVE-REQUESTS> - #<COMPILED-FUNCTION SWANK::SIMPLE-SERVE-REQUESTS> 52: <1/63> #<COMPILED-FUNCTION SWANK::SERVE-REQUESTS> - #<SWANK::CONNECTION #x203FBC26> 53: [60] unwind-protect frame 54: <1/56> #<COMPILED-FUNCTION SWANK::SERVE-CONNECTION> - #<COMPILED-FUNCTION SWANK::SETUP-SERVER-SERVE> 55: <1/51> #<COMPILED-FUNCTION SWANK::SETUP-SERVER-SERVE> - NIL 56: <1/45> #<COMPILED-FUNCTION SWANK::SETUP-SERVER> - #(NIL "/tmp/slime.19641") 57: <1/38> #<COMPILED-FUNCTION SWANK:START-SERVER> <2/37> #<SYSTEM-FUNCTION FUNCALL> 4 - SWANK:START-SERVER 58: [33] EVAL frame for form (FUNCALL (READ-FROM-STRING "swank:start-server") "/tmp/slime.19641" :CODING-SYSTEM "iso-latin-1-unix") 59: <1/30> #<SPECIAL-OPERATOR PROGN> [29] EVAL frame for form (PROGN (LOAD "/home/blake/slime/swank-loader.lisp" :VERBOSE T) (FUNCALL (READ-FROM-STRING "swank-loader:init")) (FUNCALL (READ-FROM-STRING "swank:start-server") "/tmp/slime.19641" :CODING-SYSTEM "iso-latin-1-unix")) --more--

1 0

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

20 Jul '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1371 slime/ChangeLog:1.1372 --- slime/ChangeLog:1.1371 Thu Jul 17 18:49:36 2008 +++ slime/ChangeLog Sat Jul 19 07:34:19 2008 @@ -1,3 +1,21 @@ +2008-07-19 Tobias C. Rittweiler <tcr(a)freebits.de> + + REPL shortcuts now leave an appropriate Common Lisp form in the + REPL history. + + * slime.el (slime-within-repl-shortcut-handler-p): New global. T + if truly inside a repl shortcut handler invoked by ,foo on the + REPL. + (slime-handle-repl-shortcut): Bind above global appropriatly. + (slime-repl-shortcut-eval): New; should be used in repl shortcut + handlers instead of `slime-eval'. + (slime-repl-shortcut-eval-async): New; should be used in repl + shortcut handlers instead of `slime-eval-async'. + (defslime-repl-shortcut): Update docstring. + (slime-repl-set-package): Use slime-repl-shortcut-eval. + (slime-set-default-directory): Ditto. + (slime-sync-package-and-default-directory): Ditto. + 2008-07-18 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el (slime-recompile-locations): Locations were potentially Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.108 slime/contrib/ChangeLog:1.109 --- slime/contrib/ChangeLog:1.108 Wed Jul 16 14:44:28 2008 +++ slime/contrib/ChangeLog Sat Jul 19 07:39:23 2008 @@ -1,3 +1,7 @@ +2008-07-19 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime-asdf.el (slime-oos): Use `slime-repl-shortcut-async'. + 2008-07-16 Tobias C. Rittweiler <tcr(a)freebits.de> * swank-asdf.lisp (operate-on-system-for-emacs): Wrapped in

1 0

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

18 Jul '08

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1369 slime/ChangeLog:1.1371 --- slime/ChangeLog:1.1369 Wed Jul 16 15:18:51 2008 +++ slime/ChangeLog Thu Jul 17 18:49:36 2008 @@ -1,3 +1,28 @@ +2008-07-18 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-recompile-locations): Locations were potentially + recompiled within a wrong package. Fix that. + +2008-07-18 Tobias C. Rittweiler <tcr(a)freebits.de> + + An explicit numeric value as prefix-arg given to `C-c C-c' will + now represent the debug level the defun is compiled with; + `C-u C-c C-c' defaults to maximum debug like before. (Now also + works for recompilation commands in xref buffers.) + + * slime.el (slime-compilation-debug-level): Renamed from + `slime-compile-with-maximum-debug'. + (slime-normalize-optimization-level): New. + (slime-compile-defun): Adapted accordingly. + (slime-compile-region): Ditto. + (slime-recompile-location): Added setting of debug-level. + (slime-recompile-locations): Ditto. + (slime-recompile-xref): Now takes debug-level prefix-arg. + (slime-recompile-all-xrefs): Ditto. + + * swank-sbcl.lisp (defimplementation swank-compile-string): + Adapted accordingly. + 2008-07-16 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el (slime-xref-dspec-at-point): Make more robust.

1 0

[slime-devel] Unicode characters
by Stas Boukarev 17 Jul '08

17 Jul '08

When I enter in the slime's repl (string #\u4C36), Slime enters debugger and REPL is no more usable: Debugger entered: nil (condition-case error (slime-net-read) (error (debug) (slime-net-close process t) (error "net-read error: %S" error))) slime-net-read-or-lose(#<process SLIME Lisp>) slime-process-available-input(#<process SLIME Lisp>) slime-net-filter(#<process SLIME Lisp> #("000024(:presentation-start 2 :repl-result)000024(:write-string \"\\\"\xe4\xb0\xb6\\\"\" :repl-result)000022(:presentation-end 2 :repl-result)000020(:write-string \"\n\" :repl-result)000016(:return (:ok nil) 17)" 0 66 nil 66 69 (composition (...) help-echo utf-8-help-echo untranslated-utf-8 19510) 69 192 nil)) slime-net-coding-system is 'utf-8-unix, Slime is from cvs, GNU Emacs 22.2.1 -- With Best Regards, Stas.

2 1

[slime-devel] Bug in CLEAR-INPUT
by Stelian Ionescu 17 Jul '08

17 Jul '08

If I run the example in the CLHS page of CLEAR-INPUT, Example: HU> (defun read-sleepily (&optional (clear-p nil) (zzz 0)) (list (progn (print '>) (read)) ;; Note that input typed within the first ZZZ seconds ;; will be discarded. (progn (print '>) (if zzz (sleep zzz)) (print '>>) (if clear-p (clear-input)) (read)))) READ-SLEEPILY HU> (read-sleepily t 10) > 10 > 20 30 >> End Example I get this: Recursive lock attempt #S(SB-THREAD:MUTEX :NAME "buffer read lock" :%OWNER #<SB-THREAD:THREAD "repl-thread" RUNNING {BC10BB1}> :STATE 1). [Condition of type SIMPLE-ERROR] Backtrace: 0: (SB-THREAD:GET-MUTEX #<unavailable argument> #<unavailable argument> #<unavailable argument>) 1: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-MUTEX]477)) 2: ((LAMBDA (SWANK-BACKEND::LOCK FUNCTION)) #S(SB-THREAD:MUTEX :NAME "buffer read lock" :%OWNER #<SB-THREAD:THREAD "repl-thread" RUNNING {BC10BB1}> :STATE 1) #<CLOSURE (LAMBDA NIL) {C1FDE25}>) 3: (SWANK-BACKEND:CALL-WITH-LOCK-HELD #S(SB-THREAD:MUTEX :NAME "buffer read lock" :%OWNER #<SB-THREAD:THREAD "repl-thread" RUNNING {BC10BB1}> :STATE 1) #<CLOSURE (LAMBDA NIL) {C1FDE25}>) 4: ((SB-PCL::FAST-METHOD SB-GRAY:STREAM-CLEAR-INPUT (SWANK-BACKEND::SLIME-INPUT-STREAM)) #(3 NIL 4 NIL 5 NIL) #<unused argument> #<SWANK-BACKEND::SLIME-INPUT-STREAM {B9C4011}>) 5: (CLEAR-INPUT #<SWANK-BACKEND::SLIME-INPUT-STREAM {B9C4011}>) 6: (SWANK::CLEAR-USER-INPUT) 7: (SWANK::REPL-EVAL "30 ") -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.

2 1

[slime-devel] Weird Slime Loading Behavior & Less Pretty Autodoc
by Yacin Nadji 17 Jul '08

17 Jul '08

I'm running CVS slime on Mac OS X, and I'm having some strange issues. I upgraded to CVS slime because I broke my version I had installed through macports by doing some silly upgrades of sbcl. First, SLIME-SETUP seems to load things improperly. If you take a look at my .emacs[1] you'll see I had to add (require 'slime-fuzzy) in order to get fuzzy auto-complete working. Looking at the source for what slime-fancy does, this should be auto-loaded, but it doesn't seem to work properly without manually loading it. I have a feeling this has to do with my other problem. Currently, the little function prototype helper[2] (that says the name of the function, and the name of the parameters it takes) looks a lot uglier than it used to. It used to have colors, and highlighted the current parameter I should be entering in. I realize this isn't a huge deal, but I wanted to see if it was due to using CVS slime, or if I just have something configured incorrectly. Thanks! Yacin [1] http://s3.getdropbox.com/u/10591/emacs.txt [2] http://s3.getdropbox.com/u/10591/slime-autodoc.png

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel July 2008