I said:

> I have a feature request.
> 
> Could the input URL-file please support comments. e.g:
>   http://some.host/foo.bar-1.tar   # description of file or whatever
>   http://some.host/foo.bar-2.tar   #
> 
> When I use "wget -i file", wget starts fetching:
>   http://some.host/foo.bar-1.tar%20%20
> 
> IMHO, any trailing white space should be stripped in case there's no
> comment there. Many editors (on Windows at least)  are too lazy to 
> remove it.

A correction, I do see wget stripping trailing white-space if there's no
'#' on line. I'm no expert, but guess "  #" is a legitimate part of an URL.
Or should correct encoding be "%20%20#" ?

Maybe not so easy to support comment after all...:-(

Gisle V.


Reply via email to