Quoting Jonas Smedegaard (2020-12-08 15:31:19) > Quoting Guilhem Moulin (2020-12-08 14:17:47) > > On Fri, 14 Aug 2020 at 11:40:25 +0200, Jonas Smedegaard wrote: > > > Therefore I suggest to implement what I found more intuitive: > > > > > > Setting "null-stderr = MOSTLY", treated same as YES by default, > > > > At the moment ternary options are not supported and I don't really > > like this TBH :-P --debug should probably force ‘null-stderr = No’, > > would that be acceptable to you? > > One half of what you propose - to implicitly treat null-stderr=YES as > null-stderr=YES-except-if-chatter-is-explicitly-requested is fine with > me (i.e. I don't really need an explicit and ugly-named option for it, I > just need the underlying behavior). > > The other half - that in order to get backend chatter I need to turn > general chatter "volume" to the max, is... hmmm. Better than nothing, I > guess :-/ > > > > > and option --verbose which switches it to mean no. > > > > Adding a --verbose flag for the sole purpose of overwriting > > ‘null-stderr’ is overkill IMHO, but if it were to have other effects I > > think it would be a fine addition. > > How about an option --debug-stderr or --debug-backend which enables the > backend chatter but not other debugging info?
...or use Log::Any with separate scopes (called categories in Log::Any) so that users can enable/disable/reroute/filter by scope? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
