Darshit Shah wrote: > And for future reference, you could use rate limiting to simulate a slow > connection and get the required large eta text.
As Eli wrote, I used to have this off-by-1 error too. But with the Git master, it's no longer the case. But the '--limit-rate' option (I forgot about that completely), the progress-bar seems a bit different as compared to d/l at full speed. Compare the attached image wget-progress-1.png: wget --show-progress --quiet -np -r www.watt-32.net/watt-doc/ VS wget-progress-2.png: wget --show-progress --quiet --limit-rate=2k -np -r www.watt-32.net/watt-doc/ I think it's a bit strange the final d/l speed isn't "sticky" in both cases. Is it because the speed is too high? I'm on Win-10, Wget/MSVC-2015. Captures by Greenshot: https://sourceforge.net/projects/greenshot. -- --gv
