Re: [Bug-wget] improper --no-clobber --conver-links handling

[Paul Wratt]

the result of this is --force-clobber is used

On Mon, Nov 21, 2011 at 7:43 PM, Paul Wratt <address@hidden> wrote:
> at the moment if you try a recursive wget with --no-clobber
> --convert-links the --no-clobber is discarded in favour of
> --convert-links
>
> This is incorrect as --no-clobber applies to files names on the
> server, matching filenames already downloaded, not files renamed after
> download
>
> this combination has worked for years and is required to make locally
> browsable html files from non-html web pages (eg php file managers)
>
> this is the current wget command I have been using for the last 3
> years without modifications:
>
> $ cat ~/bin/wg.sh
> #!/bin/bash
>
> wget --recursive --no-parent --level=INF --no-clobber
> --page-requisites --convert-links --html-extension
> --restrict-file-names=windows --user-agent="Mozilla/4.0 (compatible;
> MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)" $1 $2 $3 $4 $5
>
> the same command is used in wg.bat (replace %1 %2 %3 %4 %5)
>
> Paul