Read as much data as possible from IN and write it to OUT, using chunks of BUFFER-SIZE bytes. After each successful transfer of BUFFER-SIZE bytes or less, report the total number of bytes transferred to the REPORTER, which should be a <progress-reporter> object.

Given SIZE in bytes, return a string representing it in a human-readable way.

Like 'progress-reporter/file', but instead of returning human-readable progress reports, write "build trace" lines to be processed elsewhere.

Return a <progress-reporter> object to show the progress of FILE's download, which is SIZE bytes long. The progress report is written to LOG-PORT, with ABBREVIATION used to shorten FILE for display.

Return % as a string representing an ASCII-art progress bar. The total width of the bar is BAR-WIDTH.

Return a reporter that shows a progress bar every time one of the TOTAL tasks is performed. Write PREFIX at the beginning of the line.

Low-level procedure to start REPORTER.

Return a port that continuously reports the bytes read from PORT using REPORTER, which should be a <progress-reporter> object. When CLOSE? is true, PORT is closed when the returned port is closed.

When DOWNLOAD-SIZE is passed, do not read more than DOWNLOAD-SIZE bytes from PORT. This is important to avoid blocking when the remote side won't close the underlying connection.

Low-level procedure to lead REPORTER to emit a report.

Return true if PATCH is applicable to SOURCE, a directory, which corresponds to the given Guix COMMIT, a SHA1 hexadecimal string.

Apply PATCH onto SOURCE, directly modifying files beneath it.

Return a vertical space corresponding to a single blank line.

Write to PORT the expressions and blanks listed in LST.

Canonicalize COMMENT, which is to be printed at INDENT, ensuring it has the "right" number of leading semicolons.