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 http://www.gnu.org/graphics/gnu-head-banner.png -O foo the second wget would not clobber and re-get the file. Similarly, it seems odd that # wget http://www.gnu.org/graphics/gnu-head-banner.png and then # wget -N http://www.gnu.org/graphics/gnu-head-banner.png -O foo refuses to write the file named foo. I realize there are already lots of options and the interactions can be pretty confusing, but I think what I'm asking for would be of general usefulness. Maybe I'm sadistic, but -NO amuses me as a why to turn on this behavior. Perhaps just --no-clobber-output-document would be saner. Thanks for your consideration, Mitch
