[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
wget2 | Parsing of --restrict-file-names option is not consistent with
|
From: |
Bruno Manuel Rosas Marques (@bruno.m.marques) |
|
Subject: |
wget2 | Parsing of --restrict-file-names option is not consistent with WGET, accepts one option only , and not comma-separated combinations (#648) |
|
Date: |
Tue, 28 Nov 2023 18:40:18 +0000 |
Bruno Manuel Rosas Marques created an issue:
https://gitlab.com/gnuwget/wget2/-/issues/648
Parsing of --restrict-file-names option is not consistent with WGET, accepts
one option only , and not comma-separated combinations .
The flags should be ANDed after verifying incompatibilities (unix vs windows or
lowercase vs uppercase), but it should accept , for example,
--restrict-file-names=windows,lowercase -> that works in wget, not in wget2 .
--
Reply to this email directly or view it on GitLab:
https://gitlab.com/gnuwget/wget2/-/issues/648
You're receiving this email because of your account on gitlab.com.
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- wget2 | Parsing of --restrict-file-names option is not consistent with WGET, accepts one option only , and not comma-separated combinations (#648),
Bruno Manuel Rosas Marques (@bruno.m.marques) <=