[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
wget2 | no-parent option not working as expected (#620)
From: |
leex (@leex279) |
Subject: |
wget2 | no-parent option not working as expected (#620) |
Date: |
Sun, 11 Dec 2022 15:43:58 +0000 |
leex created an issue: https://gitlab.com/gnuwget/wget2/-/issues/620
I downloaded with this command:
`/opt/wget2-2.0.1/src/wget2_noinstall --fsync-policy --force-progress
--max-threads=24 --progress=bar -r -nH --no-parent --reject-regex="index.html*"
--rejec t="jpg" https://gentool.net/data/zh/2022_10_October`

According to the documentation it should only download/find everything under
/2022_10_October/, but as you can see on the screenhot, it also got
2022_11_November now.
Documentation:
-np, --no-parent
Do not ever ascend to the parent directory when retrieving recursively.
This is a useful
option, since it guarantees that **only the files below a
certain hierarchy** will be
downloaded.
--
Reply to this email directly or view it on GitLab:
https://gitlab.com/gnuwget/wget2/-/issues/620
You're receiving this email because of your account on gitlab.com.
- wget2 | no-parent option not working as expected (#620),
leex (@leex279) <=
- Re: wget2 | no-parent option not working as expected (#620), leex (@leex279), 2022/12/11
- Re: wget2 | no-parent option not working as expected (#620), @rockdaboot, 2022/12/11
- Re: wget2 | no-parent option not working as expected (#620), leex (@leex279), 2022/12/12
- Re: wget2 | no-parent option not working as expected (#620), leex (@leex279), 2022/12/12
- Re: wget2 | no-parent option not working as expected (#620), @rockdaboot, 2022/12/16
- Re: wget2 | no-parent option not working as expected (#620), leex (@leex279), 2022/12/16
- Re: wget2 | no-parent option not working as expected (#620), @rockdaboot, 2022/12/16
- Re: wget2 | no-parent option not working as expected (#620), @rockdaboot, 2022/12/16
- Re: wget2 | no-parent option not working as expected (#620), leex (@leex279), 2022/12/26
- Re: wget2 | no-parent option not working as expected (#620), leex (@leex279), 2022/12/26