Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not hide compilation output (progress and warnings) for local projects #101

Open
quicklisp opened this issue May 21, 2014 · 5 comments
Open

Comments

@quicklisp
Copy link
Owner

Quicklisp hides compilation output of its provided libraries by design. The idea is that you are not hacking on them, you are just making use of them. (You can always get verbose output by using :verbose t anyway). But you are hacking on your own local projects. Quicklisp should show all output for those projects by default, including compilation progress, style-warnings, warnings, etc.

@j3pic
Copy link

j3pic commented Nov 27, 2018

I deleted my comment because I thought I was wrong, but further research shows that I am not wrong. Either Quicklisp or ASDF captures certain warnings (but not all of them) and prevents them from being seen by handler-bind. As a result, this produces no errors if the code being loaded produces STYLE-WARNINGs at compile time:

(defmacro warnings-to-errors (&body body)
  `(handler-bind ((warning
		   (lambda (exn) (error exn))))
     ,@body))

(warnings-to-errors
  (ql:quickload :my-system :verbose t))

I've resorted to writing a program that reads my .asd file and loads the source files with load so my project can have warnings turned into errors in CI.

@quicklisp
Copy link
Owner Author

@j3pic :verbose t undoes everything Quicklisp does to muffle warnings. I'm not sure what ASDF does in addition.

@pfdietz
Copy link

pfdietz commented Aug 8, 2019

I would like the following: a version of :verbose t that ONLY affects local projects.

Even better, could there could be a way to turn on verbosity for specific systems?

@quicklisp
Copy link
Owner Author

quicklisp commented Aug 8, 2019 via email

@pfdietz
Copy link

pfdietz commented Aug 8, 2019

call-with-quiet-compilation would have to be pushed down, perhaps into apply-load-strategy, and applied on a case by case basis.

EDIT: that doesn't work. It would have to be pushed down into asdf. An around method?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants