A common debugging strategy is to study the logs.
But sometimes the program issues excessive logging messages,
necessitating the selective disabling of babbler loggers.
This SO captures the crux & solution of this Request For Enhancement:
https://stackoverflow.com/a/57002853/548792
Although the proposed SO solution of a new --disable-log option works perfectly fine,
it is annoying to have to patch every new project,
plus, it does not support auto-completion e.g. on bash.
- Would it make sense to include such capability into core code?
In any case, I'm suggesting the new option to be called --logger-disabled,
to fit with the existing option names starting with --log-....
A common debugging strategy is to study the logs.
But sometimes the program issues excessive logging messages,
necessitating the selective disabling of babbler loggers.
This SO captures the crux & solution of this Request For Enhancement:
https://stackoverflow.com/a/57002853/548792
Although the proposed SO solution of a new
--disable-logoption works perfectly fine,it is annoying to have to patch every new project,
plus, it does not support auto-completion e.g. on bash.
In any case, I'm suggesting the new option to be called
--logger-disabled,to fit with the existing option names starting with
--log-....