No control over debugging
Currently debugging can only be enabled or disabled. There is no additional control over debugging like the level.
Designs
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Author Owner
Pass two or three arguments to the debugging function
- Minimum debug level
- Maximum debug level
- Debug message
1 and 2 above need more thought and one of these may be removed.
Debug function will check these arguments against externally supplied parameter by the user's command, and output only if eligible.
Add value to the debug parameter (
-d
). This value will be desired debug level. Propose the following five levels:-
0
: Force quiet -
1
: Error only -
2
: Warning and exit status (default) -
3
: Summary info on various stages of the scripts -
4
: Verbose
Edited by username-removed-169778 - username-removed-169778 changed milestone to %v01.02.00
changed milestone to %v01.02.00
- Author Owner
This is related to #5
- username-removed-169778 mentioned in issue #5
mentioned in issue #5
- Author Owner
Since this changes the debug argument from being a switch to a param-value pair, this will break compatibility with previous versions. So it will be carried out at the next major version release.
- username-removed-169778 changed milestone to %v02.00.00
changed milestone to %v02.00.00
- username-removed-169778 added Stage_Proposal label
added Stage_Proposal label
- username-removed-169778 added Severity_Minor label
added Severity_Minor label
- username-removed-169778 added Category_Core label
added Category_Core label
- username-removed-169778 marked this issue as related to #5
marked this issue as related to #5
- Author Owner
Each debug message carries a weight, based on the list above.
If the debug level of the message is less than the requested debug level, then the message is displayed, else suppressed.