The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
Provides a progress bar similar to 'dplyr' that can write progress out to a variety of locations, including stdout(), stderr(), or from file(). Useful when using 'knitr' or 'rmarkdown', and you still want to see progress of calculations in the terminal.
| Version: | 1.1.0 |
| Imports: | R6, R.oo |
| Suggests: | knitr, rmarkdown, purrr, testthat, covr, mockr, withr, parallel |
| Published: | 2018-02-20 |
| Author: | Robert M Flight [aut, cre], Hadley Wickham [ctb] (Author of included dplyr fragments), Romain Francois [ctb] (Author of included dplyr fragments), Lionel Henry [ctb] (Author of included dplyr fragments), Kirill Müller [ctb] (Author of included dplyr fragments), RStudio [cph] (Copyright holder of included dplyr fragments) |
| Maintainer: | Robert M Flight <rflight79 at gmail.com> |
| BugReports: | https://github.com/rmflight/knitrProgressBar/issues |
| License: | MIT + file LICENSE |
| URL: | https://rmflight.github.io/knitrProgressBar |
| NeedsCompilation: | no |
| Materials: | README NEWS |
| CRAN checks: | knitrProgressBar results |
| Reference manual: | knitrProgressBar.pdf |
| Vignettes: |
Example Progress Bar Output Progress for Multi-Processing |
| Package source: | knitrProgressBar_1.1.0.tar.gz |
| Windows binaries: | r-devel: knitrProgressBar_1.1.0.zip, r-release: knitrProgressBar_1.1.0.zip, r-oldrel: knitrProgressBar_1.1.0.zip |
| macOS binaries: | r-release (arm64): knitrProgressBar_1.1.0.tgz, r-oldrel (arm64): knitrProgressBar_1.1.0.tgz, r-release (x86_64): knitrProgressBar_1.1.0.tgz, r-oldrel (x86_64): knitrProgressBar_1.1.0.tgz |
| Old sources: | knitrProgressBar archive |
Please use the canonical form https://CRAN.R-project.org/package=knitrProgressBar to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.