Re: [Bug-wget] Re: wget manpage question/suggestion

[Micah Cowan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matthew Woehlke wrote:
> Micah Cowan wrote:
>> As far as I'm concerned, the single biggest shortcoming of the current
>> manpage, is its lack of coverage for the wgetrc commands, particularly
>> those that lack command-line option counterparts.
> 
> As a random passer-by, I'll point out that it is not uncommon (and IMO a
> good thing) to document such in 'wgetrc.1' rather than 'wget.1'
> (preferably with See Also note, of course).

In general, I agree with that; in specific, I'm on the fence a bit.

The reason that rc files tend to get a manpage to themselves, is that it
tends to be a very large bit of separate documentation. In the case of
wget, the vast majority of wgetrc options have command-line option
equivalents, and in fact the bulk of the wgetrc documentation in the
Texinfo docs currently just refer the reader to the equivalent
command-line option for the details. ~95% of the wgetrc options could be
documented, simply by noting the wgetrc command name along with the
already-present command-line option(s). The remaining commands are
things like http_proxy, and robots.

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
Maintainer of GNU Wget and GNU Teseq
http://micah.cowan.name/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpt7VIACgkQ7M8hyUobTrE0lACff3sqEWXUixJmzo+KJvt6wTNc
1xcAn3xAq53Dz0j1ZNLrj2n+3Rv27Bde
=+CZ1
-----END PGP SIGNATURE-----