-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

A bug was submitted to Ubuntu's Malone bugtracker, complaining that
- --background shoud not create a wget-log file when --quiet has been
specified:

  https://bugs.launchpad.net/ubuntu/+source/wget/+bug/135063
  https://savannah.gnu.org/bugs/index.php?20917

This seems reasonable to me, despite the fact that there are a few logs
that can still be issued, even when --quiet is specified: the likelihood
of needing those is much lower than the likelihood that the user will be
irritated by an empty wget.log appearing whenever they use --background,
if --quiet was specified :)

Stefan Lendl <[EMAIL PROTECTED]> has been good enough to prepare a
patch to resolve this issue; however, we did run across a potential
issue. If --server-response is enabled, even if --quiet was specified,
FTP server responses will still be issued (however, HTTP server
responses will _not_ be).

First of all, this is obviously an inconsistency: we should pick one
behavior or the other for FTP and HTTP alike. Second, which is the
correct behavior? Is it reasonable to expect that someone issuing
- --quiet -S actually wants the server responses (and nothing else), or
should --quiet override -S (or, even conflict with it)?

It seems to me, that a person wanting not much more output than -S will
still be wanting -nv to say so, rather than -q. --quiet seems like it
should be, well, quiet. Unless the sky is falling.

If we take out the server responses from --quiet, then the only message
it would ever issue would be for xmalloc failure. I think we can live
with that not showing up in backgrounded wgets (after all, if they
wanted to be notified when something went wrong, well, they wouldn't
issue --quiet, now would they? :) )

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG2Tqu7M8hyUobTrERCK4CAJ9swVEkvutDflD5FOj9xddT2YOYXACfXZN2
wb9tXQHz4lGPjH0YYf/nSa8=
=DZPf
-----END PGP SIGNATURE-----

Reply via email to