[asdf-devel] asdf verbosity

Robert Goldman rpgoldman at sift.info
Tue Apr 26 21:31:24 UTC 2011


On 4/26/11 Apr 26 -1:06 PM, Faré wrote:
>>> OK. Should I turn verbose off by default, or should I make verbose
>>> less verbose, or introduce several degrees of verbosity?
>>
>> I would be pretty happy if the old behavior was reinstated, and nothing
>> else was changed.
>>
> OK. Reverted in 2.014.12, with some additional changes.
> 
>> Was there a specific problem that prompted the change in behavior?
>>
> I sometimes want to debug a ASDF build, or find out what file a set of
> style-warnings come from, etc. At ITA we use ancillary methods that call
> explain. I wanted to have something similar part of ASDF itself. I guess
> however, that the fact that ASDF is "verbose" by default, makes that
> more annoying than helpful.
> 
> What about making ASDF *not* verbose by default? Does anyone simultaneously
> care to have ASDF print the little it currently prints yet not the progress
> report I was printing?

I have never found the ASDF message printing burdensome.  But then, I
don't ever build as many systems at once as Xach does.

Is there some way to tell if this is other than a quicklisp-specific
problem?  If it is quicklisp-specific, could we just support a special
configuration for QL that doesn't hide information from people using
ASDF in a more limited environment?  QL is almost defined as one where
you don't expect the user to be able to debug parent systems.  I'm a lot
more familiar with /needing/ to debug parent systems!

Best,
r




More information about the asdf-devel mailing list