Skip to content

Compatibility with non-tty devices#10

Merged
nex3 merged 2 commits into
jfelchner:masterfrom
jim:optional-tty
Dec 16, 2011
Merged

Compatibility with non-tty devices#10
nex3 merged 2 commits into
jfelchner:masterfrom
jim:optional-tty

Conversation

@jim

@jim jim commented Dec 16, 2011

Copy link
Copy Markdown
Contributor

We have several scripts we use during application development that monitor long running processes with ruby-progressbar. We also have these scripts running in automated environments (such as CI), and the output in these situations is very noisy. We could alter the scripts, but I think it would be nicer if this library could gracefully handle these situations.

This patch adds a baseline behavior in non-tty environments so that things like log files aren't filled with every frame of the progress bar animation.

jim added 2 commits December 16, 2011 14:03
…output strategy when it is not.

Use IO.tty? to make this determination.

This is really only useful for some ProgressBars. ReverseProgressBar and using
file_transfer_mode don't make much sense when writing to a non-terminal device.
nex3 added a commit that referenced this pull request Dec 16, 2011
Compatibility with non-tty devices
@nex3 nex3 merged commit 4283f72 into jfelchner:master Dec 16, 2011
@jfelchner

Copy link
Copy Markdown
Owner

@jim I'd love to get this ported over to the rewrite on the development branch. Is there any way you could let me know what the specifications are or, better yet, create a pull request with some failing specs?

Any assistance you could give me would be fantastic. And thanks again for the contribution.

@jim

jim commented Jul 31, 2012

Copy link
Copy Markdown
Contributor Author

@jfelchner I can try to write some failing specs for you (and hopefully even some code that fixes them).

@github-actions

Copy link
Copy Markdown

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions Bot added the outdated Inactive - Outdated label Dec 28, 2020
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Dec 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

outdated Inactive - Outdated

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants