Please open a bug about this.
Is this a regression from old ASDF 1? If it is, make it a asdf 2 milestone, otherwise an asdf 2.1 milestone.
At ITA, we have local extensions to control the ASDF output. I'll have to dig into the topic someday.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] How many big company employees does it take to enact a one-liner change to a system configuration file? At least one engineer per horizontal layer in the organization, plus each of their managers, and then some — but in the end everyone's ass will be covered.
On 13 April 2010 11:18, Jean-Claude Beaudoin jean.claude.beaudoin@gmail.com wrote:
Hello all,
In ASDF2 (I am still using 1.661) is it possible turn off all "informational" output in one single operation?
Looking at the source I see that there is a bunch of :verbose arguments to most (all?) of ASDF main entry points, but each of these have hard coded default values of T. This way one has to pass a ":verbose NIL" pair on each call to ASDF in order to get silence.
Couldn't we have a *asdf-verbose* global that would give the default value of those :verbose arguments?
Then a single (setq *asdf-verbose* nil) would allow the whole thing to go in "run silent, run deep" mode.
Thanks Jean-Claude Beaudoin