We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I run zstd v1.4.4 as a cron job, and I get a progress bar output even when the stdout and stderr are not tty:
zstd --rm -19 $FILENAME 2>&1 | logger
Zstd tries to draw the progress bar, as a result I see this in the journal:
[386B blob data]
It would be best to imply -q when the stdout/stderr are not a tty. Or at least print \n instead of \r as a separator between the lines.
-q
\n
\r
The text was updated successfully, but these errors were encountered:
I think implying -q when stderr is not a TTY would make sense.
stderr
Sorry, something went wrong.
binhdvo
No branches or pull requests
I run zstd v1.4.4 as a cron job, and I get a progress bar output even when the stdout and stderr are not tty:
Zstd tries to draw the progress bar, as a result I see this in the journal:
It would be best to imply
-q
when the stdout/stderr are not a tty. Or at least print\n
instead of\r
as a separator between the lines.The text was updated successfully, but these errors were encountered: