In that case, the filename would need to be output to stderr as well, at least once per file. At the moment, for each file, the filename seems to be output only once to the stdout. All messages related to the file follow in subsequent lines; the warning and error messages don't contain the filename.<br>
<br><div class="gmail_quote">On 22 October 2010 15:53, Ulrich Windl <span dir="ltr"><<a href="mailto:Ulrich.Windl@rz.uni-regensburg.de">Ulrich.Windl@rz.uni-regensburg.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
>>> Kal Sze <<a href="mailto:swordangel@gmail.com">swordangel@gmail.com</a>> schrieb am 22.10.2010 um 09:33 in Nachricht<br>
<AANLkTi=WXKZbkcwXPvpjSMgFs2BeA=fmoOWTsuh9=<a href="mailto:Vbs@mail.gmail.com">Vbs@mail.gmail.com</a>>:<br>
<div><div></div><div class="h5">> Hello,<br>
><br>
> I want to check my collection of hundreds of ogg files for potential<br>
> problems. As far as I know, "ogginfo -v" is as comprehensive as it gets.<br>
> However, using the "-v" option causes the output to be VERY VERY long when<br>
> there are hundreds of files to check. I need a way to skim the output and<br>
> only look at warnings and errors. In order to do that I need to know the<br>
> complete list of warnings and errors that can be output by ogginfo. Does<br>
> anybody have that list handy? Are they *all* contained in the ogginfo2.c<br>
> source code file? I see a lot of warning-related or error-related strings in<br>
> there, but I can't be sure that there are not more strings borrowed from<br>
> other source files.<br>
<br>
</div></div>Hi!<br>
<br>
It would be helpful if errors were sent to stderr, while other messages were sent to stdout. Otherwise you'll have to use grep to filter messages.<br>
<br>
Regards,<br>
Ulrich<br>
<br>
><br>
> Cheers,<br>
> Kal<br>
><br>
<br>
<br>
<br>
<br>
</blockquote></div><br>