I had to make a decision. If curl estimates time left to transfer a file is 4398046511103 seconds. How do we display that in - 7 bytes?
I decided that if the time exceeds 99,999 years we show it as ">99999y" even though a 63bit epoch *can* hold up to 292 billion years.
7 bytes because I need the entire curl progress meter to fit within 79 bytes.
What's a better thing to do on a Saturday? 😁
github.com/curl/curl/pull/2017…
progress: narrower time display, multiple fixes by bagder · Pull Request #20173 · curl/curl
Each time field is now 7 characters wide, so that the total width never exceeds 79 columns so that it works correctly also in Windows terminals. The title lines are adjusted accordingly. This is ac...GitHub
Mister Wanko
in reply to daniel:// stenberg:// • • •varx/social
in reply to daniel:// stenberg:// • • •synlogic4242
in reply to daniel:// stenberg:// • • •Noisytoot
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Noisytoot • • •Hugo 雨果
in reply to daniel:// stenberg:// • • •Ciourte Piaille
in reply to daniel:// stenberg:// • • •Fubaroque
in reply to daniel:// stenberg:// • • •I would call it “huge”. That will avoid all and any misinterpretation.
#fourbytes
Daniel Böhmer
in reply to daniel:// stenberg:// • • •When you write 7 or 79 "bytes" do you mean [ASCII] characters or is there some technical limit of storage??
Not meant to nitpick, actually confused. Maybe because I'm not a C programmer but Perl very well knows about byte length and string length🤔
Edit: missed the PR link before posting. The PR makes it all clear. My bad!
Jan Walzer
in reply to daniel:// stenberg:// • • •