Re: url-encoding in the wiki - Re: [Bug-wget] [BUG?] Ampersand (&) in url?

[Micah Cowan]

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

augustin wrote:
> There is no mention of url encoding in the manual.

Not sure what url encoding has to do with this discussion. We're talking
about shell quoting here.

> I think this kind of stuff should be documented in the wiki. I can at least 
> help with that.
> http://wget.addictivecode.org/Wget
> First, I wonder where in the wiki to put this. I don't want to overburden the 
> FAQ page. I am thinking to create a new section for contribution by the 
> members of this list about advanced usage.

The FAQ is where this sort of thing belongs, if it belongs anywhere.
It's definitely not "advanced usage"; in fact, it has nothing to do with
Wget usage at all. It's purely to do with your shell. The only thing
remotely related to Wget about it is that perhaps you're more likely to
try to give Wget arguments with ampersands in them than you are for
other programs.

This is also why I'm not interested in patching the manpage: if you
started with wget, then _every_ single command-line app would also need
that same patch. It's not even universally true (there are probably
shells that don't use the ampersand specially). Better to just know what
characters are special to your shell, and deal with them accordingly.

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

iEYEARECAAYFAkkdobQACgkQ7M8hyUobTrFObQCfWSdkFxOcOVH5YdxeUAkd1UbL
R8YAnRzdLdzyAen0E1u2WCo5tcaAXE/P
=Z0Jy
-----END PGP SIGNATURE-----