Being a computer geek, I tend to like things organized
in tables so options stand out. I took the time to rewrite
the text for the --progress section of the manpage, as
it was always difficult for me to find the values and
differences for the different subtags. Looking at the
--progress=type, it doesn't quickly stand out what the
possible values are nor that there are . I tended more
toward a BNF type specification, but the central change is
making the style types stand out. So even if you don't
like the exact wording, I do think the table format presents
the style options more clearly (i.e. they stand out quickly
note, output of man was used as template for the changes, so
this isn't directly applicable as a patch. I hope that isn't
a block to the change, as it seems simple enough but I don't
currently have a subversion source tree setup nor do I know
manpage source syntax by memory (not a frequently used source
language ;^) ):
--progress=style
Legal styles are bar[:force] and dot[:dotsize].
The bar style is used by default. It draws an
ASCII progress bar graphics (a.k.a thermometer
display) indicating the status of retrieval. If the
output is not a TTY, the dot style will be used.
To force bar usage when output is not a TTY, use
the :force tag (i.e. --progress=bar:force )
The dot style traces traces the retrieval by printing
dots on the screen, each dot representing a fixed
amount of downloaded data.
An optional dotsize tag can be specified to change
the the amount of downloaded data per dot, grouping
and line as follows (K = 1024 bytes; M = 1024KBytes ):
size per dots per
dotsize dot linegroup line
- --- -
default 1K 50K 1050
binary 8K 384K 1648
mega64K3M 848
default is used if no dotsize tag is specified.
Note that you can set per user defaults using the
progress command in .wgetrc. Note: specifying
an option on the command line overrides .wgetrc
settings.
