Re: [Bug-wget] giga progress report suggestion

[Giuseppe Scrivano]

Hi Karl,

I think it should be already there.

If you specify:

./wget --progress=dot:giga -O/dev/null http://server/large/file

then each line is 32MB.  I think this is not documented, this patch
should fix it:

diff --git a/doc/wget.texi b/doc/wget.texi
index 288059e..fed188a 100644
--- a/doc/wget.texi
+++ b/doc/wget.texi
@@ -715,9 +715,12 @@ different meaning to one dot.  With the @code{default} 
style each dot
 represents 1K, there are ten dots in a cluster and 50 dots in a line.
 The @code{binary} style has a more ``computer''-like orientation---8K
 dots, 16-dots clusters and 48 dots per line (which makes for 384K
-lines).  The @code{mega} style is suitable for downloading very large
+lines).  The @code{mega} style is suitable for downloading large
 files---each dot represents 64K retrieved, there are eight dots in a
 cluster, and 48 dots on each line (so each line contains 3M).
+If @code{mega} is not enough then you can use the @code{giga}
+style---each dot represents 1M retrieved, there are eight dots in a
+cluster, and 32 dots on each line (so each line contains 32M).
 
 Note that you can set the default style using the @code{progress}
 command in @file{.wgetrc}.  That setting may be overridden from the


Thanks for your report!

address@hidden (Karl Berry) writes:

> Hi Giuseppe and all,
>
> May I suggest a `giga' option for dot_style (ramp everything up another
> order of magnitude or so), or a way to make it configurable?  E.g.,
> maybe if the value is a number, that is how many K each dot represents?
>
> These days, files get larger and larger.  I often use wget from scripts
> to download 40-50mb files, which takes a dozen lines of progress reports
> (usually zooming by).  I'd just as soon have it take one or two lines ...
>
> Just a thought ...
>
> Thanks,
> Karl
>

-- 
Giuseppe