|
From: Florian K. <fl...@ei...> - 2015-05-20 13:53:39
|
On 19.05.2015 23:23, Philippe Waroquiers wrote: > On Tue, 2015-05-19 at 17:33 +0200, Julian Seward wrote: >> I was thinking about moving error-count printing to its own flag >> >> --show-error-counts=no|yes [no] >> Seems a bit of an ad-hoc solution. And we already have MANY command line options. I agree with Philippe that the logging stuff needs to be redone so we can select what we want to see and at what levels of detail. Adding more observability would also be good fo unit testing.. Something like --vtrace=<component>:<level of detail> e.d. --vtrace=signals:2 or --vtrace=aspacemgr:4 I don't think this would be that much work to do, actually, given sufficient supply of beer which can always be arranged.... What would be more work is to decide what kinds of messages are meant for users and what are for developers... I'd say: if you can reasonably filter the output, go for that. Florian |