Re: [Bug-wget] Wget on Windows handling of wildcards

2018-06-06 Thread Eli Zaretskii
> From: Sam Habiel > Date: Wed, 6 Jun 2018 08:27:44 -0400 > Cc: bug-wget@gnu.org > > Is there a valid argument to be made that some arguments for wget > should not be expanded, like accept and reject? Probably. The problem is that wildcard expansion of the command line doesn't understand the

Re: [Bug-wget] Wget on Windows handling of wildcards

2018-06-06 Thread Sam Habiel
Gisle, I downloaded it from here: https://eternallybored.org/misc/wget/. It doesn't seem to be MinGW compiled; but I can't tell. Eli, Holy shit it works! I spent several hours trying different combinations--but never came up with this incantation! Thank you so much! Is there a valid argument

Re: [Bug-wget] Wget on Windows handling of wildcards

2018-06-05 Thread Eli Zaretskii
> From: Sam Habiel > Date: Tue, 5 Jun 2018 14:16:27 -0400 > > I have a wget command that has a -A flag that contains a wildcard. > It's '*.DAT'. That works fine on Linux. I am trying to get the same > thing to run on Windows, but *.DAT keeps getting expanded by wget (cmd > does no expansion

[Bug-wget] Wget on Windows handling of wildcards

2018-06-05 Thread Sam Habiel
First time poster. I have a wget command that has a -A flag that contains a wildcard. It's '*.DAT'. That works fine on Linux. I am trying to get the same thing to run on Windows, but *.DAT keeps getting expanded by wget (cmd does no expansion itself). There is no way that I found of suppressing