LogBuffer can now use a separate filter object to decide whether a log entry should be entered into the buffer or not.
Added LogFilter with fine-grained filtering parameters that allow for per-domain minimum levels and developer messages. App stores its log filter in the persistent Config as the record “log.filter”.
Added the -vv and -vvv options to more conveniently enable the verbosity level. If these try to go beyond ‘extra verbose’, the developer messages are enabled automatically. The -devlog and -nodevlog options enable/disable the developer messages separately.
Also, the Config module was cleaned up by moving the constants for Log and Updater into their own modules. This way the constants are not saved persistently.
Added by skyjake almost 11 years ago
Added by
Log|libdeng2|Client: Filtering log entries
LogBuffer can now use a separate filter object to decide whether
a log entry should be entered into the buffer or not.
Added LogFilter with fine-grained filtering parameters that allow
for per-domain minimum levels and developer messages. App stores
its log filter in the persistent Config as the record “log.filter”.
Added the -vv and -vvv options to more conveniently enable the
verbosity level. If these try to go beyond ‘extra verbose’, the
developer messages are enabled automatically. The -devlog and
-nodevlog options enable/disable the developer messages separately.
Also, the Config module was cleaned up by moving the constants
for Log and Updater into their own modules. This way the constants
are not saved persistently.