Per our discussion on the #email_archives Slack channel, it would make more sense for the progress bar to print to /dev/tty rather than to stderr.
Currently, the progress bar is getting printed to stderr, which makes it visible by default. However, if the user redirects stderr to a file, which they may want to do in order to carefully inspect the error messages, then the progress bar is silenced. (The reason for this is that our current progress bar-printing function only prints conditionally on stderr being a tty.)
It should probably instead implement the following logic:
if stderr is a tty, do what we do now and print to stderr
otherwise, if /dev/tty can't be opened, do nothing
Per our discussion on the
#email_archivesSlack channel, it would make more sense for the progress bar to print to/dev/ttyrather than tostderr.Currently, the progress bar is getting printed to
stderr, which makes it visible by default. However, if the user redirectsstderrto a file, which they may want to do in order to carefully inspect the error messages, then the progress bar is silenced. (The reason for this is that our current progress bar-printing function only prints conditionally onstderrbeing atty.)It should probably instead implement the following logic:
stderris atty, do what we do now and print tostderr/dev/ttycan't be opened, do nothing/dev/ttycan be opened, open and print to it