The '--quiet' option does not silence errors about exiv2

[clanmills]

The message is coming from the exiv2(.exe) application and not the library.

574 rmills@rmillsmbp:~/gnu/exiv2/0.26 $ grep 'No Exif data found in the file' src/actions.cpp 
                      << _("No Exif data found in the file\n");
            if (noExif) std::cerr << path_ << ": " << _("No Exif data found in the file\n");
                      << ": " << _("No Exif data found in the file\n");
                      << ": " << _("No Exif data found in the file\n");
                      << ": " << _("No Exif data found in the file\n");
                      << ": " << _("No Exif data found in the file\n");
                      << ": " << _("No Exif data found in the file\n");
575 rmills@rmillsmbp:~/gnu/exiv2/0.26 $

Perhaps the application should also respect the log level of the library. If the library has been silenced, perhaps applications should also keep silent.

How much pain is this causing? Can you just use exiv2 --quiet cabin.jpg 2>/dev/null

If you want me to investigate further, can you attach cabin.jpg so that I reproduce your use case.

[00vareladavid]

I just assumed the expected behavior would be a clear stderr under the --quiet option. I'm not sure of the utility of the current behavior when using the CLI. Overall, I just wanted to bring it to your attention since the workaround (redirecting to /dev/null) is straightforward. (Slightly tangential question: if the library is being silenced, does this mean something else is writing the error messages?)

[clanmills]

Yes. The message is being written by the Exiv2 cli application. The library has been silenced.

[clanmills]

I'll reopen this issue if you wish to discuss this further.