On Thu, Jan 19, 2023 at 11:11 AM Marcin Błażejowski
<marcin(a)wrzosy.nsb.pl> wrote:
On 19.01.2023 16:48, Cottrell, Allin wrote:
> My feeling is that neither --quiet nor even --silent as applied to
> individual commands should suppress warnings; they're about reducing
> or eliminating regular output.
Ok. But printing warnings in numerical methods (like optimizers) might
be seen as some kind of debugging. If so, suppressing any messages could
be an option.
Debugging messages should go to stderr. Conversely, if a warning
appears in the regular output it should be something that the user
ought to know about.
It's possible that this policy is not implemented with full
consistency, but if so the right fix is to redirect any messages that
really ought to be going to stderr, not to multiply obscure options.
Allin