[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 1790 in lilypond: Proper loglevels: cmd-line option --loglevel=NON
From: |
lilypond |
Subject: |
Issue 1790 in lilypond: Proper loglevels: cmd-line option --loglevel=NONE/ERROR/WARN/PROGRESS/INFO/DEBUG |
Date: |
Sat, 30 Jul 2011 22:14:52 +0000 |
Status: Accepted
Owner: address@hidden
Labels: Type-Enhancement Patch-new
New issue 1790 by address@hidden: Proper loglevels: cmd-line option
--loglevel=NONE/ERROR/WARN/PROGRESS/INFO/DEBUG
http://code.google.com/p/lilypond/issues/detail?id=1790
Proper loglevels: cmd-line option
--loglevel=NONE/ERROR/WARN/PROGRESS/INFO/DEBUG
Allow the user to specify which messages (s)he wants to see on stderr:
The lilypond code basically stays the same, I only added a loglevel
global variable, which is used in the warning/error*/progress*/success
functions (ly:warning, ly:error, etc. in Scheme). If the proper level
is not set for a message, it is not printed.
There are only two larger changes:
-) Global var be_verbose_global replaced by loglevel (much finer-grained)
-) New functions (full)debug_output, which replaces code like:
if (be_verbose_global) {
progress_indication (...)
}
All changes were done to warn.cc and to the member of the Input class
(apparently, we have two parallel error-reporting "frameworks" in
lilypond...).
Note for all functions in warn.cc (not for the members of Input):
The debug_output function (and progress_indication and message) have
an optional argument to specify whether the output of the message
should always start on a new line or continue the previous output.
Documentation for this new feature is still missing (both in the AU
as well as in the CG)
- Issue 1790 in lilypond: Proper loglevels: cmd-line option --loglevel=NONE/ERROR/WARN/PROGRESS/INFO/DEBUG,
lilypond <=