mirror/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-01-27 01:44:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

_PROGRESS.md: add the E unit, mention kibibyte

Browse Source 
The suffixes used are not standard since we want them to be single
characters and the proper ones would be KiB, MiB etc.

Closes #19502
This commit is contained in:
Daniel Stenberg 2025-11-12 23:15:37 +01:00
parent 4b2da75bca
commit c6eb9bb3dc
No known key found for this signature in database
GPG Key ID: 5CC908FDB71E12C2
2 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
.github/scripts/pyspelling.words vendored
View File

@ -244,6 +244,7 @@ et
etag
ETag
ETags
exa
exe
executables
EXPN
@ -417,6 +418,7 @@ kerberos
Keychain
keychain
KiB
kibibyte
kickstart
Kirei
Knauf
@ -491,6 +493,7 @@ Mavrogiannopoulos
Mbed
mbedTLS
md
mebibyte
Meglio
memdebug
MesaLink

11
docs/cmdline-opts/_PROGRESS.md
View File

@ -4,9 +4,10 @@
curl normally displays a progress meter during operations, indicating the
amount of transferred data, transfer speeds and estimated time left, etc. The
progress meter displays the transfer rate in bytes per second. The suffixes
(`k` for kilo, `M` for mega, `G` for giga, `T` for tera, and `P` for peta) are
1024 based. For example 1k is 1024 bytes. 1M is 1048576 bytes.
progress meter displays the transfer rate in bytes per second. The used
suffixes (`k` for kilo, `M` for mega, `G` for giga, `T` for tera, `P` for peta
and `E` for exa) are 1024 based. For example 1k is 1024 bytes. 1M is 1048576
bytes. Strictly speaking this makes the units kibibyte and mebibyte etc.
curl displays this data to the terminal by default, so if you invoke curl to
do an operation and it is about to write data to the terminal, it *disables*
@ -14,8 +15,8 @@ the progress meter as otherwise it would mess up the output mixing progress
meter and response data.
If you want a progress meter for HTTP POST or PUT requests, you need to
redirect the response output to a file, using shell redirect (\>), --output
or similar.
redirect the response output to a file, using shell redirect (\>), --output or
similar.
This does not apply to FTP upload as that operation does not spit out any
response data to the terminal.