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.
Search by keywords in R packages, task views, CRAN, the web and display the results in the console or in txt, html or pdf files. Download the package documentation (html index, README, NEWS, pdf manual, vignettes, source code, binaries) with a single instruction. Visualize the package dependencies and CRAN checks. Compare the package versions, unload and install the packages and their dependencies in a safe order. Explore CRAN archives. Use the above functions for task view maintenance. Access web search engines from the console thanks to 80+ bookmarks. All functions accept standard and non-standard evaluation.
Version: | 5.1.4 |
Depends: | R (≥ 3.4.0) |
Imports: | brew, latexpdf, networkD3, sig, sos, XML |
Suggests: | ctv, findR, foghorn, knitr, pacman, rmarkdown, xfun |
Published: | 2024-03-03 |
DOI: | 10.32614/CRAN.package.RWsearch |
Author: | Patrice Kiener |
Maintainer: | Patrice Kiener <rpackages at inmodelia.com> |
License: | GPL-2 |
NeedsCompilation: | no |
Language: | en-GB |
Materials: | README NEWS |
CRAN checks: | RWsearch results |
Reference manual: | RWsearch.pdf |
Vignettes: |
V1: Introduction to RWsearch V2: Display and download the documentation V3: Package versions and dependencies V4: Tools for task views V5: Web search engines |
Package source: | RWsearch_5.1.4.tar.gz |
Windows binaries: | r-devel: RWsearch_5.1.4.zip, r-release: RWsearch_5.1.4.zip, r-oldrel: RWsearch_5.1.4.zip |
macOS binaries: | r-release (arm64): RWsearch_5.1.4.tgz, r-oldrel (arm64): RWsearch_5.1.4.tgz, r-release (x86_64): RWsearch_5.1.4.tgz, r-oldrel (x86_64): RWsearch_5.1.4.tgz |
Old sources: | RWsearch archive |
Please use the canonical form https://CRAN.R-project.org/package=RWsearch 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.