- rc.debug.hooks and rc.debug.parser are now valid settings.  They are
  not yet obeyed.
This commit is contained in:
Paul Beckingham 2014-10-04 19:20:38 -04:00
parent a71d4f1596
commit fa22cff5be
3 changed files with 16 additions and 3 deletions

View file

@ -450,9 +450,20 @@ debug output can be useful. It can also help explain how the command line is
being parsed, but the information is displayed in a developer-friendly, not a
user-friendly way.
.TP
.B debug.hooks=0
Controls the hook system diagnostic level. Level 0 means no diagnostics.
Level 1 shows hook call and status. Level 2 also shows I/O.
.TP
.B debug.parser=0
Controls the parser diagnostic level. Level 0 means no diagnostics. Level 1
shows the parse tree. Level 2 shows expression evaluation details.
.TP
.B debug.tls=0
Controls the GnuTLS log level. For 'sync' debugging.
Controls the GnuTLS diagnostic level. For 'sync' debugging. Level 0 means no
diagnostics. Level 9 is the highest.
.TP
.B alias.rm=delete

View file

@ -768,10 +768,10 @@ void Context::propagateDebug ()
config.set ("debug.tls", 2);
if (! config.has ("debug.hooks"))
config.set ("debug.hooks", 2);
config.set ("debug.hooks", 1);
if (! config.has ("debug.parser"))
config.set ("debug.parser", 2);
config.set ("debug.parser", 1);
}
}

View file

@ -134,6 +134,8 @@ int CmdShow::execute (std::string& output)
" dateformat.info"
" dateformat.report"
" debug"
" debug.hooks"
" debug.parser"
" debug.tls"
" default.command"
" default.due"