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

[slime-devel] patch for ABCL to (more) correctly report source location for COMPILE-CONDITION
by Mark Evenson 19 Oct '08

19 Oct '08

swank-abcl.lisp (handle-compile-warning): Report source location position when we can. Use NAMESTRING for *compile-filename*. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now." Index: swank-abcl.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-abcl.lisp,v retrieving revision 1.58 diff -u -r1.58 swank-abcl.lisp --- swank-abcl.lisp 17 Oct 2008 21:26:53 -0000 1.58 +++ swank-abcl.lisp 19 Oct 2008 15:02:17 -0000 @@ -127,7 +127,6 @@ (defimplementation local-port (socket) (java:jcall (java:jmethod "java.net.ServerSocket" "getLocalPort") socket)) - (defimplementation close-socket (socket) (ext:server-socket-close socket)) @@ -263,7 +262,6 @@ (defimplementation frame-locals (index) `(,(list :name "??" :id 0 :value "??"))) - (defimplementation frame-catch-tags (index) (declare (ignore index)) nil) @@ -306,8 +304,11 @@ (in-package :swank-backend) (defun handle-compiler-warning (condition) - (let ((loc nil));(getf (slot-value condition 'excl::plist) :loc))) - (unless (member condition *abcl-signaled-conditions*) ; filter condition signaled more than once. + (let ((loc (when (and jvm::*compile-file-pathname* + system::*source-position*) + (cons jvm::*compile-file-pathname* system::*source-position*)))) + ;; filter condition signaled more than once. + (unless (member condition *abcl-signaled-conditions*) (push condition *abcl-signaled-conditions*) (signal (make-condition 'compiler-condition @@ -325,7 +326,7 @@ (list :position (1+ pos))))) (t (make-location - (list :file *compile-filename*) + (list :file (namestring *compile-filename*)) (list :position 1))))))))) (defvar *abcl-signaled-conditions*)

2 1

[slime-devel] Swank sbcl error - patch attached
by jcm＠sdf.lonestar.org 17 Oct '08

17 Oct '08

Type fixed: Index: swank-sbcl.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-sbcl.lisp,v retrieving revision 1.224 diff -u -r1.224 swank-sbcl.lisp --- swank-sbcl.lisp 16 Oct 2008 21:15:28 -0000 1.224 +++ swank-sbcl.lisp 17 Oct 2008 17:18:29 -0000 @@ -467,7 +467,7 @@ (defimplementation swank-compile-file (pathname load-p external-format) (handler-case - (multiple-value-bind (output-file warnigns-p failure-p) + (multiple-value-bind (output-file warnings-p failure-p) (with-compilation-hooks () (compile-file pathname :external-format external-format)) (values output-file warnings-p

2 1

[slime-devel] swank-require not implemented in kawa (current svn)
by Matthew D. Swank 16 Oct '08

16 Oct '08

I know kawa is not a regularly supported back end, but could someone give me away around: java.lang.Error: swank-require not implemented [type java.lang.Error] Restarts: 0: [quit] terminate current thread Backtrace: 0: ferror$V ("~a not implemented" ["swank-require"]) 1: lookupSlimefun (|swank:swank-require| gnu.kawa.slib.srfi$Mnhash$Mntable@ca56214) 2: $PcEval ((|swank:swank-require| (quote ({(keywords)}swank-asdf {(keywords)}swank-package-fu {(keywords)}swank-fuzzy {(keywords)}swank-fancy-inspector {(keywords)}swank-arglists))) #<environment user>) 3: listenerLoop (chan@b035079 #<environment user> #<output-port>) 4: listener (chan@b035079 #<environment user>) 5: lambda6 (chan@b035079) 6: apply1 (#<procedure gnu.expr.ModuleMethod> chan@b035079) 7: applyN (#<procedure gnu.expr.ModuleMethod> [chan@b035079]) 8: applyN ([chan@b035079]) 9: applyN ([#<procedure gnu.expr.ModuleMethod> chan@b035079]) 10: apply2 (#<procedure gnu.expr.ModuleMethod> chan@b035079) 11: lambda55 () 12: apply0 (#<procedure gnu.expr.ModuleMethod>) 13: apply0 () 14: run () 15: run () Locals: this = Thread[swank-listener,5,main] Thanks, Matt -- "You do not really understand something unless you can explain it to your grandmother." -- Albert Einstein.

1 1

[slime-devel] backtrace write-string to wrong stream
by Willem Broekema 16 Oct '08

16 Oct '08

(For some reason a previous copy of this mail did not make it to the list.) Some backtrace output ended up in the REPL buffer. - Willem --- swank.lisp 03 Oct 2008 16:45:57 +0200 1.597 +++ swank.lisp 04 Oct 2008 12:43:27 +0200 @@ -120,7 +120,7 @@ (#\return (write-string "\\r" stream)) (t (write-char c stream)))) (write-char #\" stream)) - (t (write-string string))))) + (t (write-string string stream))))) (set-pprint-dispatch 'string #'escape-string 0 table) table)))

2 1

[slime-devel] getting emacs debugger in latest slime with Allegro...?
by Gary King 16 Oct '08

16 Oct '08

This is with the cvs head of slime and Allegro Common Lisp. Not always but often, when I choose to compile a file via c-x c-k, the compile happens and then I get tossed in the emacs lisp debugger with a message similar to: 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> "000029(:write-string \"; No value\" :repl-result)000017(:return (:ok nil) 961)") once this has happened, just about every interaction with slime provides the same (or similar) bug. To stop it, I must quick the slime session and restart it. This started happening a few days ago after I updated. It's very irritating. (to say the least) -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

2 1

[slime-devel] a different flashing function for `slime-compile-region'
by Yoni Rabkin 13 Oct '08

13 Oct '08

Hello, This patch to slime.el makes the `slime-compile-region' flash a more subtle effect. I'm using it, and thought that someone else might enjoy it as well. Maybe a cleaner implementation would be to call a `slime-flashing-function', to allow different flashing styles to be changed more easily. -- "Cut your own wood and it will warm you twice"

1 0

[slime-devel] Kawa Support
by Volkan YAZICI 12 Oct '08

12 Oct '08

Hi, Is there problem with the contrib/swank-kawa.scm? COMPILE-FILE in Kawa 1.9.1 REPL complains that gnu.text.SyntaxException: /home/vy/elisp/slime/contrib/swank-kawa.scm:2062:1: '(* 1 st$unit)' is not a valid identifier at kawa.lib.system.compileFile(system.scm:94) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at gnu.expr.PrimProcedure.apply(PrimProcedure.java:251) at gnu.mapping.CallContext.runUntilDone(CallContext.java:251) at gnu.expr.ModuleExp.evalModule(ModuleExp.java:296) at kawa.Shell.run(Shell.java:230) at kawa.Shell.run(Shell.java:172) at kawa.Shell.run(Shell.java:159) at kawa.repl.main(repl.java:844) Regards.

3 5

[slime-devel] convert-standard-filename causing invalid syntax
by Thomas Karolski 12 Oct '08

12 Oct '08

When trying to compile a file from slime (with slime-compile-and-load-file) I get the following error: PARSE-NAMESTRING: syntax error in filename "g:\\Programme\\cygwin\\home\\Joreji\\opengl-test.lisp" at position 2 This is due to the convert-standard-filename function which slime-to-lisp-filename-function is set to (with the recent cvs revision). Once I change slime-to-lisp-filename-function to #'identity it all works again (well, the way it "works" on windows anyway, heh). Is it possible PARSE-NAMESTRING has difficulties with the backslash ("\") ? I'm using: GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-09-09 on LENNART-69DE564 (patched) Cygwin on Windows XP Recent (updated 10 minutes ago) version of cvs slime (though the change to convert-standard-filename has been made a few days ago as I see it). Regards, Thomas K.

2 4

[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

Re: [slime-devel] output from sbcl threads
by Helmut Eller 11 Oct '08

11 Oct '08

* Michael Weber [2008-10-10 13:07+0200] writes: > On Oct 10, 2008, at 11:20 , Giovanni Gigante wrote: > >> (sb-thread:make-thread (lambda () (format t "hello world"))) >> >> on the REPL I get something like >> #<SB-THREAD:THREAD FINISHED values: NIL {A72C609}> >> >> but the "hello world" part goes to the --dribble-file on the remote >> machine. >> Is it possible to have that on the REPL too? > > You could bind the output stream lexically: > > CL-USER> (let ((s *standard-output*)) > (sb-thread:make-thread (lambda () (format s "hello > world")))) > #<SB-THREAD:THREAD RUNNING {15833191}> > hello world > CL-USER> Alternatively you could set swank:*globally-redirect-io* or swank:*default-worker-thread-bindings*. Helmut.

1 0