-
-
Notifications
You must be signed in to change notification settings - Fork 939
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[input-file] Allow comments after a URL #2808
Comments
Debatable... I think it's pretty straightforward to understand.
Yes, this is by design? I mean, some kind of delimiter has to used..
Yes, this is actually how it's supposed to be, though.. |
everything after the first " #" (space + hash) gets ignored
Personally I add blank lines between comment-URL-blocks, so that I can triple click URLs without having anything extra selected
True, but gallery-dl can usually handle both, url-escaped and -unescaped, versions of a URL. |
Thanks. I think When you have hundreds of URL (for regular downloading of recently added content with
|
Thank you. Works fine with some extractors. However, it does not work with Pixiv if there are more than one space character before
gallery-dl/gallery_dl/__init__.py Lines 98 to 101 in 2ed5802
An example fix: if " #" in line or "\t#" in line:
line = re.split("[ \t]+#", line, 1)[0] |
Sorry for the oversight. I must've only tested with URLs where extra whitespace/characters after a URL don't matter and just assumed it would work for all. Fixed in bdad9c4 |
There is a minor bug (with bdad9c4) in case when you use
|
I would like to add comments in the input file (
--input-file
) after a URL. After" #"
(" "
a space character (one or more) and"#"
)For example:
For this gallery-dl currently prints the error:
The follow format is working, but it looks less readable:
More over it already expects only one URL per line, I can't to do:
There is also no valid URL with a "plain" space character. The space character is present either with
%20
or with+
(in the search params) in a URL.Addition (why I noted these two things):
...so it will not be the breaking change.
The text was updated successfully, but these errors were encountered: