Add example for downloading a list of URLs from a file

[samueloph]

I haven't thoroughly tested this and checked for corner cases yet, but does it make sense to document this usecase in the manpage?

Pending:

• Check corner cases, e.g.: whitespaces, carriage return, breaklines, tabs...
• Check non GNU/Linux portability.

[bagder]

curl has native support from downloading a "URL list" with --url @file. I could be worth looking at what it would take for wcurl to offer that too.

[sergiodj]

I haven't thoroughly tested this and checked for corner cases yet, but does it make sense to document this usecase in the manpage?

I think this is more a shell script example than a wcurl example, TBH. The way wcurl is being invoked is exactly the same as you would do with a single URL, so there's nothing new for the user here (except how to make a loop in their shell, if they don't know yet).

[XhmikosR]

There's an extra space before the backticks, there should be two :)

[samueloph]

I'm still not yet sure whether it's a good idea to list this in the docs, it feels clunky due to the fact that this is just documenting how to write shellscript and not exactly a wcurl feature.

I wonder if it's really useful.

I'll keep this open while I make a decision.

[samueloph]

curl has native support from downloading a "URL list" with --url @file. I could be worth looking at what it would take for wcurl to offer that too.

Hmm, today, if one calls wcurl @input_file.txt, wcurl will set --output index.html, resulting in the first file of the list being named index.html, but still downloading everything.

But then even if we dropped --output when the URL starts with @ and let curl handle the list of URLs, we lose features like percent-decoding the URLs and their resulting filenames, plus the default filename of index.html for when curl can't infer one.

It's not great as this make wcurl behave differently whether the input is a file or URLs.

I don't think solving this without relying on curl's parsing of @file is too hard, but I want to approach a solution for this very carefully, considering whether it's really worth the extra code and what should be the UX (@file? -i/--input-file? both?).

I'll give it a go at a few ways to solve this and if I'll push a PR if I end up with anything that I'm happy with.

Edit - I've got it, will publish a PR soon.

[samueloph]

I've published a PR with a proposal for how to achieve the input-file feature.

#66