If -O output file and -N are both specified, it seems like there should be some
mode where
the tests for noclobber apply to the output file, not the filename that exists
on the remote machine.
So, if I run
# wget -N http://www.gnu.org/graphics/gnu-head-banner.png -O foo
and then
# wget -N
Hi, many-respected all!
Recently, playing with wget on win32 (version 1.10.2, downloaded from
http://users.ugent.be/~bpuype/wget/ ), I have encountered a problem
which I'd like to share with ya.
When I do
wget -O - http://foo/bar
the stream I get on STDOUT is corrupt.
Let's say, I do
wget
From: Mitch Silverstein
If -O output file and -N are both specified [...]
When -O foo is specified, it's not a suggestion for a file name to
be used later if needed. Instead, wget opens the output file (foo)
before it does anything else. Thus, it's always a newly created file,
and hence
