Adjust the wording as pv does not "know" things.

This commit is contained in:
Andrew Wood
2026-04-21 22:18:13 +01:00
parent a955038360
commit a220e993af
2 changed files with 7 additions and 8 deletions
+5 -6
View File
@@ -879,12 +879,11 @@ This is because of the way sparse output is achieved, and the file will be
the correct size when the transfer ends.
.PP
If \fBpv\fR is writing to a pipe, and the command reading that pipe exits,
\fBpv\fR will only know that has happened when it \fInext\fR receives some
input data to transfer.
So \*(lq\fBecho\~|\~pv\~|\~sleep\~1\fR\*(rq will wait forever, but
\*(lq\fB{\~echo;\~sleep\~3;\~echo;\~}\~|\~pv\~|\~sleep\~1\fR\*(rq will
end after 3 seconds when \fBpv\fR tries to transfer the second line of
input.
\fBpv\fR can only discover that has happened when it \fInext\fR receives
some input data to transfer.
Therefore \*(lq\fBecho\~|\~pv\~|\~sleep\~1\fR\*(rq will wait forever, but
\*(lq\fB{\~echo;\~sleep\~3;\~echo;\~}\~|\~pv\~|\~sleep\~1\fR\*(rq will end
after 3 seconds when \fBpv\fR tries to transfer the second line of input.
.\"
.SH REPORTING BUGS
Please report bugs or feature requests via the issue tracker linked from the
+2 -2
View File
@@ -832,8 +832,8 @@ reports progress. This is because of the way sparse output is achieved,
and the file will be the correct size when the transfer ends.
If **pv** is writing to a pipe, and the command reading that pipe exits,
**pv** will only know that has happened when it *next* receives some
input data to transfer. So "**echo \| pv \| sleep 1**" will wait
**pv** can only discover that has happened when it *next* receives some
input data to transfer. Therefore "**echo \| pv \| sleep 1**" will wait
forever, but "**{ echo; sleep 3; echo; } \| pv \| sleep 1**" will end
after 3 seconds when **pv** tries to transfer the second line of input.