(Using slime with sbcl here)
For asdf systems that have warnings or errors when compiling, slime-load-system is a little less helpful than I'd hope for; I get the slime debugger before I get the nice tree view of what happened. Which is problematic, because I don't know if it's okay to tell asdf to continue, until I know what went wrong. Anyone have a workaround for this? Would it be difficult to get the tree view along with the debugger?
I should really familiarize myself better with the slime sources.
I think I just solved my own problem here.
--- swank-backend.lisp.~1.49.~ Tue Jun 8 17:18:38 2004 +++ swank-backend.lisp Tue Jun 8 17:56:56 2004 @@ -196,7 +196,8 @@ (definterface operate-on-system (system- (operation (find-symbol operation-name :asdf))) (when (null operation) (error "Couldn't find ASDF operation ~S" operation-name)) - (apply operate operation system-name keyword-args)))) + (handler-bind ((warning #'error)) + (apply operate operation system-name keyword-args)))))
(definterface swank-compile-file (filename load-p) "Compile FILENAME signalling COMPILE-CONDITIONs.
"Thomas F. Burdick" tfb@OCF.Berkeley.EDU writes:
(Using slime with sbcl here)
For asdf systems that have warnings or errors when compiling, slime-load-system is a little less helpful than I'd hope for; I get the slime debugger before I get the nice tree view of what happened. Which is problematic, because I don't know if it's okay to tell asdf to continue, until I know what went wrong. Anyone have a workaround for this? Would it be difficult to get the tree view along with the debugger?
As a workaround you can call M-x slime-list-compiler-notes manually. The Lisp side keeps the warnings around until the next compile.
Helmut.
-
Helmut Eller -
Thomas F. Burdick