Lasse Collin wrote: > On 2010-03-21 Jonathan Nieder wrote: >> 100.0 % 10,000 GiB / 10,000 GiB = 1.000 999 KiB/s 9 h 40 min >> 9999:50:50 (less padding, more units) > > Maybe. The units have to be MiB when compressing, because otherwise the > sizes won't get updated frequently enough to see that some progress is > happening. They can be MiB also after successful operation, because then > no extra space is needed for estimated remaining time. So the only > situation where GiB or TiB would be used is after an error or user > pressing C-c.
Oh, interesting. Thanks for the explanation. > I suggest showing the estimated remaining time if the user has pressed > C-c and in all other cases keep the current behavior. That would definitely be an improvement: it would solve Trent’s problem. I admit I don’t really like it, since it doesn’t solve the other problems: - The sudden switch from time remaining to elapsed time is confusing, since all the user sees is the time displayed jumping down and no longer changing - On any error that doesn’t have to do with malformed data, it is nice to know how both how much time elapsed and how much time was remaining. Really, the relevant statistic is estimated total time to compress or decompress. But I can send a separate patch later to fix those. > Would this be good enough solution? Yes, I think so. Thanks. Sorry for the long delay, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
