My bad on STDOUT. I actually knew this (as can be seen with 2>&1 on my
redirects).

Either way. Forcing the output to a progress bar gives a very unintelligible
result. It's messy due to the control characters that has to be sent to
"clear" the line for the new bar to be printed. Here's an example:
^M 0% [                                     ] 0
--.--K/s             ^M 5% [>                                    ]
2,351,152     11.21M/s             ^M10%
[==>                                  ] 4,705,600     11.22M/s
^M15% [====>                                ] 7,060,048
11.22M/s             ^M21% [======>                              ]
9,414,496     11.22M/s             ^M26%
[========>                            ] 11,768,944    11.22M/s
^M31% [==========>                          ] 14,123,392
11.22M/s             ^M36% [============>                        ]
16,477,840    11.22M/s             ^M42%
[==============>                      ] 18,832,288    11.22M/s
^M47% [================>                    ] 21,186,736
11.22M/s             ^M52% [==================>                  ]
23,541,184    11.22M/s             ^M58%
[====================>                ] 25,895,632    11.22M/s
^M63% [======================>              ] 28,250,080
11.22M/s             ^M68% [========================>            ]
30,603,080    11.22M/s             ^M73%
[==========================>          ] 32,957,528    11.22M/s
^M79% [============================>        ] 35,311,976    11.22M/s    ETA
00:00^M84% [==============================>      ] 37,666,424    11.22M/s
ETA 00:00^M89% [================================>    ] 40,020,872
11.22M/s    ETA 00:00^M95% [==================================>  ]
42,375,320    11.22M/s    ETA
00:00^M100%[====================================>] 44,546,403    11.22M/s
ETA 00:00

It gives an eta, but not a friendly output.

Maybe having another "--progress" option like "dot:witheta". This might be a
bit stupid. I wouldn't have done it this way. Personally I feel a
--eta[=<yes|no|auto>] or something would work well.

Q

On Tue, Dec 9, 2008 at 7:50 AM, Micah Cowan <[EMAIL PROTECTED]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Quintin Beukes wrote:
> > The output looks like this:
> >  4600K .......... .......... .......... .......... .......... 94%
> > 30.13 KB/s
> >  4650K .......... .......... .......... .......... .......... 95%
> > 29.28 KB/s
> >  4700K .......... .......... .......... .......... .......... 96%
> > 24.13 KB/s
> >
> >
> > What's missing though is an "ETA" for completion like STDOUT has.
>
> Hi. Tried using a newer version of Wget, >= 1.11 ? :)
>
> Alternatively, you can add --progress=bar:force to force the same output
> as you normally get on a terminal (which, FWIW, is actually on stderr).
>
> - --
> Micah J. Cowan
> Programmer, musician, typesetting enthusiast, gamer.
> GNU Maintainer: wget, screen, teseq
> http://micah.cowan.name/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkk+BxEACgkQ7M8hyUobTrERPACgiVuuXE6xSipD/1yzCasYNewi
> K3gAn3wTjgIIGV6al1WaOqJ/upYDiDkM
> =j0mW
> -----END PGP SIGNATURE-----
>



-- 
Quintin Beukes

Reply via email to