"Ian Abbott" <[EMAIL PROTECTED]> writes:

> On 5 Apr 2002 at 18:17, Noel Koethe wrote:
>
>> Will this be changed so the user could use -nv with >/dev/null
>> and get only errors or warnings displayed?
>
> So what I think you want is for any log message tagged as
> LOG_VERBOSE (verbose information) or LOG_NONVERBOSE (basic
> information) in the source to go to stdout when no log file has been
> specified and the `-O -' option has not been used and for everything
> else to go to stderr?

That change sounds dangerous.  Current Wget output doesn't really have
a concept of "errors" that would be really separate from other output;
it only operates on the level of "verbosity".  This was, of course, a
bad design decision, and I agree that steps need to be taken to change
it.  I'm just not sure that this is the right step.

For one, I don't know of any utility that splits its output this way.
It is true that many programs print their output on stdout and errors
to stderr, but Wget's log output is hardly the actual, programmatic,
output of the program.  That can only be the result of `-O -'.

Suddenly `wget -o X' is no longer equivalent to `wget 2>x', which
violates the Principle of Least Surprise.

Reply via email to