Hi,
I wonder if there is a way to filter or structure compiler output in the REPL buffer, similar to when compiling a form or file through editor commands (C-c C-c). I am thinking of a situation when I run a form which triggers compilation of many files (like when using mini- modue from GBBopen). The output goes directly to the REPL buffer and is hard to browse (mostly warnings and notes).
Roman
Roman Budzianowski roman.j@budzianowski.net writes:
Hi,
I wonder if there is a way to filter or structure compiler output in the REPL buffer, similar to when compiling a form or file through editor commands (C-c C-c). I am thinking of a situation when I run a form which triggers compilation of many files (like when using mini- modue from GBBopen). The output goes directly to the REPL buffer and is hard to browse (mostly warnings and notes).
Use the ,cl (compile-and-load) REPL shortcut; if you use the `slime-asdf' contrib, you can also use ,load-system to load a registered ASD file.
-T.
I was not clear. I have to evaluate
(mini-module::compile-module :pq-core :propagate :recompile)
to compile my system. The output goes to REPL buffer.
I was wondering if the functionality of REPL buffer can be extended to parse the compiler output and display it in more intelligent way.
Roman
On Mar 21, 2008, at 3:54 AM, Tobias C. Rittweiler wrote:
Roman Budzianowski roman.j@budzianowski.net writes:
Hi,
I wonder if there is a way to filter or structure compiler output in the REPL buffer, similar to when compiling a form or file through editor commands (C-c C-c). I am thinking of a situation when I run a form which triggers compilation of many files (like when using mini- modue from GBBopen). The output goes directly to the REPL buffer and is hard to browse (mostly warnings and notes).
Use the ,cl (compile-and-load) REPL shortcut; if you use the `slime-asdf' contrib, you can also use ,load-system to load a registered ASD file.
-T.
slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel
Roman Budzianowski roman.j@budzianowski.net writes:
I was not clear. I have to evaluate
(mini-module::compile-module :pq-core :propagate :recompile)
to compile my system. The output goes to REPL buffer.
You can place that form in a buffer (cf. M-x slime-scratch), and perform a C-c C-c on it. Or you can do a M-x slime-compile-defun explicitly at the REPL.
Alternatively, you can write your own REPL shortcut (see `defslime-repl-shortcut') that does something like
(slime-eval-async `(swank::swank-compiler (cl:lambda () (mini-module::compile-module ,modulename ,@args))) (slime-make-compilation-finished-continuation (current-buffer)))
I was wondering if the functionality of REPL buffer can be extended to parse the compiler output and display it in more intelligent way.
We don't parse the compiler output, but rely on special compiler-note conditions being signalled by the compiler.
-T.
-
Roman Budzianowski -
Tobias C. Rittweiler