}: if \code{TRUE} then PDF images are only
included in the PDF manual, and SVG images are only included in the HTML
manual. (This only applies to images supplied via markdown.)
}
}
\section{How to set}{
Either set in \code{DESCRIPTION}:
\if{html}{\out{}}\preformatted{Roxygen: list(markdown = TRUE, load = "installed")
}\if{html}{\out{
}}
Or if longer, you can put in \verb{/man/roxygen/meta.R}:
\if{html}{\out{}}\preformatted{list(
markdown = TRUE,
load = "installed"
)
}\if{html}{\out{
}}
}
\keyword{internal}
roxygen2/man/tags_list.Rd 0000644 0001762 0000144 00000000477 14264333036 015076 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/tag-metadata.R
\name{tags_list}
\alias{tags_list}
\alias{tags_metadata}
\title{Access metadata about built-in tags}
\usage{
tags_list(built_in = TRUE)
tags_metadata()
}
\description{
Access metadata about built-in tags
}
\keyword{internal}
roxygen2/man/load.Rd 0000644 0001762 0000144 00000003137 14525717717 014034 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/load.R
\name{load}
\alias{load}
\alias{load_pkgload}
\alias{load_installed}
\alias{load_source}
\title{Load package code}
\usage{
load_pkgload(path)
load_installed(path)
load_source(path)
}
\arguments{
\item{path}{Path to source package}
}
\description{
roxygen2 is a dynamic documentation system, which means it works with the
objects inside your package, not just the source code used to create them.
These functions offer various ways of loading your package to suit various
constraints:
\itemize{
\item \code{load_pkgload()} uses \code{pkgload::load_all()} to simulate package loading
as closely as we know how. It offers high fidelity handling of code that
uses S4, but requires that the package be compiled.
\item \code{load_source()} simulates package loading by attaching packages listed in
\code{Depends} and \code{Imports}, then sources all files in the \verb{R/} directory.
This was the default strategy used in roxygen2 6.0.0 and earlier;
it's primary advantage is that it does not need compilation.
\item \code{load_installed()} uses the installed version of the package. Use this
strategy if you have installed a development version of the package
already. This is the highest fidelity strategy, but requires work
outside of roxygen2.
}
You can change the default strategy for your function with roxygen2 \code{load}
option. Override the default off \code{pkgload} to use the \code{source} or
\code{installed} strategies:
\if{html}{\out{}}\preformatted{Roxygen: list(load = "source")
}\if{html}{\out{
}}
}
roxygen2/man/tag_parsers.Rd 0000644 0001762 0000144 00000002740 13545643447 015425 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/tag-parser.R
\name{tag_parsers}
\alias{tag_parsers}
\alias{tag_value}
\alias{tag_inherit}
\alias{tag_name}
\alias{tag_two_part}
\alias{tag_name_description}
\alias{tag_words}
\alias{tag_words_line}
\alias{tag_toggle}
\alias{tag_code}
\alias{tag_examples}
\alias{tag_markdown}
\alias{tag_markdown_with_sections}
\title{Parse tags}
\usage{
tag_value(x)
tag_inherit(x)
tag_name(x)
tag_two_part(x, first, second, required = TRUE, markdown = TRUE)
tag_name_description(x)
tag_words(x, min = 0, max = Inf)
tag_words_line(x)
tag_toggle(x)
tag_code(x)
tag_examples(x)
tag_markdown(x)
tag_markdown_with_sections(x)
}
\arguments{
\item{x}{A \link{roxy_tag} object to parse}
\item{first, second}{Name of first and second parts of two part tags}
\item{required}{Is the second part required (TRUE) or can it be blank
(FALSE)?}
\item{markdown}{Should the second part be parsed as markdown?}
\item{min, max}{Minimum and maximum number of words}
}
\value{
A \link{roxy_tag} object with the \code{val} field set to the parsed value.
}
\description{
These functions parse the \code{raw} tag value, convert a string into a richer R
object and storing it in \code{val}, or provide an informative warning and
returning \code{NULL}.
}
\section{New tag}{
To create a new \verb{@mytag} define \code{roxy_tag_parse.roxy_tag_mytag()}. It should
either call one of the functions here, or directly set \code{x$val}.
}
\keyword{internal}
roxygen2/man/tags-index-crossref.Rd 0000644 0001762 0000144 00000003565 14550054451 016774 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/tag-metadata.R
\name{tags-index-crossref}
\alias{tags-index-crossref}
\alias{@aliases}
\alias{@backref}
\alias{@concept}
\alias{@family}
\alias{@keywords}
\alias{@references}
\alias{@seealso}
\title{Tags for indexing and cross-references}
\usage{
#' @aliases ${1:alias}
#' @backref ${1:path}
#' @concept ${1:concept}
#' @family ${1:family name}
#' @keywords ${1:keyword}
#' @references ${1:reference}
#' @seealso [${1:func}()]
}
\description{
Learn the full details in \code{vignette('index-crossref')}.
Key tags:
\itemize{
\item \verb{@aliases $\{1:alias\}}: Add additional aliases to the topic.
Use \code{NULL} to suppress the default alias automatically generated by roxygen2.
\item \verb{@concept $\{1:concept\}}: Add additional keywords or phrases to be included in the \code{help.search()} index. Each \verb{@concept} should be a single term or phrase.
\item \verb{@family $\{1:family name\}}: Generate \verb{@seealso} entries to all other functions in \verb{family name}.
\item \verb{@keywords $\{1:keyword\}}: Add a standardised keyword, indexed by \code{help.search()}. These are generally not useful apart from \verb{@keywords internal} which flags the topic as internal and removes from topic indexes.
\item \verb{@references $\{1:reference\}}: Pointers to the related literature. Usually formatted like a bibliography.
\item \verb{@seealso [$\{1:func\}()]}: Link to other related functions or urls. Usually a sentence or two, or a bulleted list.
}
Other less frequently used tags:
\itemize{
\item \verb{@backref $\{1:path\}}: Manually override the backreference that points from the \code{.Rd} file back to the source \code{.R} file. Only needed when generating code.
}
}
\seealso{
Other documentation tags:
\code{\link{tags-rd}},
\code{\link{tags-rd-other}},
\code{\link{tags-reuse}}
}
\concept{documentation tags}
roxygen2/man/RoxyTopic.Rd 0000644 0001762 0000144 00000020530 14262717326 015043 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/topic.R
\name{RoxyTopic}
\alias{RoxyTopic}
\title{A \code{RoxyTopic} is an ordered collection of unique rd_sections}
\description{
A \code{RoxyTopic} object corresponds to a generated \code{.Rd} file.
}
\keyword{internal}
\section{Public fields}{
\if{html}{\out{}}
\describe{
\item{\code{sections}}{Named list of sections. Each item must be an
\code{\link[=rd_section]{rd_section()}} object.}
\item{\code{filename}}{Path to the \code{.Rd} file to generate.}
}
\if{html}{\out{
}}
}
\section{Methods}{
\subsection{Public methods}{
\itemize{
\item \href{#method-RoxyTopic-format}{\code{RoxyTopic$format()}}
\item \href{#method-RoxyTopic-is_valid}{\code{RoxyTopic$is_valid()}}
\item \href{#method-RoxyTopic-has_section}{\code{RoxyTopic$has_section()}}
\item \href{#method-RoxyTopic-get_section}{\code{RoxyTopic$get_section()}}
\item \href{#method-RoxyTopic-get_value}{\code{RoxyTopic$get_value()}}
\item \href{#method-RoxyTopic-get_rd}{\code{RoxyTopic$get_rd()}}
\item \href{#method-RoxyTopic-get_name}{\code{RoxyTopic$get_name()}}
\item \href{#method-RoxyTopic-inherits_from}{\code{RoxyTopic$inherits_from()}}
\item \href{#method-RoxyTopic-inherits_section_from}{\code{RoxyTopic$inherits_section_from()}}
\item \href{#method-RoxyTopic-add}{\code{RoxyTopic$add()}}
\item \href{#method-RoxyTopic-add_section}{\code{RoxyTopic$add_section()}}
\item \href{#method-RoxyTopic-clone}{\code{RoxyTopic$clone()}}
}
}
\if{html}{\out{
}}
\if{html}{\out{}}
\if{latex}{\out{\hypertarget{method-RoxyTopic-format}{}}}
\subsection{Method \code{format()}}{
Format the \code{.Rd} file. It considers the sections in
particular order, even though Rd tools will reorder them again.
\subsection{Usage}{
\if{html}{\out{}}\preformatted{RoxyTopic$format(...)}\if{html}{\out{
}}
}
\subsection{Arguments}{
\if{html}{\out{}}
\describe{
\item{\code{...}}{Passed to the \code{format()} methods of the \code{\link[=rd_section]{rd_section()}}
objects, the sections.}
}
\if{html}{\out{
}}
}
\subsection{Returns}{
Character string.
}
}
\if{html}{\out{
}}
\if{html}{\out{}}
\if{latex}{\out{\hypertarget{method-RoxyTopic-is_valid}{}}}
\subsection{Method \code{is_valid()}}{
Check if an \code{.Rd} file is valid
\subsection{Usage}{
\if{html}{\out{}}\preformatted{RoxyTopic$is_valid()}\if{html}{\out{
}}
}
\subsection{Returns}{
Logical flag, \code{TRUE} for valid \code{.Rd} files
}
}
\if{html}{\out{
}}
\if{html}{\out{}}
\if{latex}{\out{\hypertarget{method-RoxyTopic-has_section}{}}}
\subsection{Method \code{has_section()}}{
Check if an \code{.Rd} file has a certain section.
\subsection{Usage}{
\if{html}{\out{}}\preformatted{RoxyTopic$has_section(type)}\if{html}{\out{
}}
}
\subsection{Arguments}{
\if{html}{\out{}}
\describe{
\item{\code{type}}{Section type, a character scalar.}
}
\if{html}{\out{
}}
}
\subsection{Returns}{
Logical flag.
}
}
\if{html}{\out{
}}
\if{html}{\out{}}
\if{latex}{\out{\hypertarget{method-RoxyTopic-get_section}{}}}
\subsection{Method \code{get_section()}}{
Query a section.
\subsection{Usage}{
\if{html}{\out{}}\preformatted{RoxyTopic$get_section(type)}\if{html}{\out{
}}
}
\subsection{Arguments}{
\if{html}{\out{}}
\describe{
\item{\code{type}}{Section type, a character scalar.}
}
\if{html}{\out{
}}
}
\subsection{Returns}{
The \link{rd_section} object representing the section, or \code{NULL}
if the topic has no such section.
}
}
\if{html}{\out{
}}
\if{html}{\out{}}
\if{latex}{\out{\hypertarget{method-RoxyTopic-get_value}{}}}
\subsection{Method \code{get_value()}}{
Query the value of a section. This is the value of
the \link{rd_section} object.
\subsection{Usage}{
\if{html}{\out{}}\preformatted{RoxyTopic$get_value(type)}\if{html}{\out{
}}
}
\subsection{Arguments}{
\if{html}{\out{}}
\describe{
\item{\code{type}}{Section type, a character scalar.}
}
\if{html}{\out{
}}
}
\subsection{Returns}{
Value.
}
}
\if{html}{\out{
}}
\if{html}{\out{}}
\if{latex}{\out{\hypertarget{method-RoxyTopic-get_rd}{}}}
\subsection{Method \code{get_rd()}}{
Get the Rd code of a section.
\subsection{Usage}{
\if{html}{\out{}}\preformatted{RoxyTopic$get_rd(type)}\if{html}{\out{
}}
}
\subsection{Arguments}{
\if{html}{\out{}}
\describe{
\item{\code{type}}{Section type, a character scalar.}
}
\if{html}{\out{
}}
}
\subsection{Returns}{
Character vector, one element per line.
}
}
\if{html}{\out{
}}
\if{html}{\out{}}
\if{latex}{\out{\hypertarget{method-RoxyTopic-get_name}{}}}
\subsection{Method \code{get_name()}}{
Get the value of the \code{name} section. This is the name
of the Rd topic.
\subsection{Usage}{
\if{html}{\out{}}\preformatted{RoxyTopic$get_name()}\if{html}{\out{
}}
}
\subsection{Returns}{
Character scalar.
}
}
\if{html}{\out{
}}
\if{html}{\out{}}
\if{latex}{\out{\hypertarget{method-RoxyTopic-inherits_from}{}}}
\subsection{Method \code{inherits_from()}}{
Query the topics this topic inherits \code{type} from.
\subsection{Usage}{
\if{html}{\out{}}\preformatted{RoxyTopic$inherits_from(type)}\if{html}{\out{
}}
}
\subsection{Arguments}{
\if{html}{\out{}}
\describe{
\item{\code{type}}{Section type, a character scalar.}
}
\if{html}{\out{
}}
}
\subsection{Returns}{
A character vector of topic names.
}
}
\if{html}{\out{
}}
\if{html}{\out{}}
\if{latex}{\out{\hypertarget{method-RoxyTopic-inherits_section_from}{}}}
\subsection{Method \code{inherits_section_from()}}{
Query the topics this topic inherits sections from.
\subsection{Usage}{
\if{html}{\out{}}\preformatted{RoxyTopic$inherits_section_from()}\if{html}{\out{
}}
}
\subsection{Returns}{
A character vector of topic names.
}
}
\if{html}{\out{
}}
\if{html}{\out{}}
\if{latex}{\out{\hypertarget{method-RoxyTopic-add}{}}}
\subsection{Method \code{add()}}{
Add one or more sections to the topic.
\subsection{Usage}{
\if{html}{\out{}}\preformatted{RoxyTopic$add(x, block = "???", overwrite = FALSE)}\if{html}{\out{
}}
}
\subsection{Arguments}{
\if{html}{\out{}}
\describe{
\item{\code{x}}{Section(s) to add. It may be
another \code{RoxyTopic} object, all of its sections will be added;
or an \link{rd_section} object;
or a list of \link{rd_section} objects to add.}
\item{\code{block}}{Name of block to use in error messages.}
\item{\code{overwrite}}{Whether to overwrite an existing section. If \code{FALSE}
then the two sections will be merged.}
}
\if{html}{\out{
}}
}
}
\if{html}{\out{
}}
\if{html}{\out{}}
\if{latex}{\out{\hypertarget{method-RoxyTopic-add_section}{}}}
\subsection{Method \code{add_section()}}{
Add a section.
\subsection{Usage}{
\if{html}{\out{}}\preformatted{RoxyTopic$add_section(section, block = "???", overwrite = FALSE)}\if{html}{\out{
}}
}
\subsection{Arguments}{
\if{html}{\out{}}
\describe{
\item{\code{section}}{\link{rd_section} object to add.}
\item{\code{block}}{Name of block to use in error messages.}
\item{\code{overwrite}}{Whether to overwrite an existing section. If \code{FALSE}
then the two sections will be merged.}
}
\if{html}{\out{
}}
}
\subsection{Details}{
Ensures that each type of name (as given by its name), only appears
once in \code{self$sections}. This method if for internal use only.
}
}
\if{html}{\out{
}}
\if{html}{\out{}}
\if{latex}{\out{\hypertarget{method-RoxyTopic-clone}{}}}
\subsection{Method \code{clone()}}{
The objects of this class are cloneable with this method.
\subsection{Usage}{
\if{html}{\out{}}\preformatted{RoxyTopic$clone(deep = FALSE)}\if{html}{\out{
}}
}
\subsection{Arguments}{
\if{html}{\out{}}
\describe{
\item{\code{deep}}{Whether to make a deep clone.}
}
\if{html}{\out{
}}
}
}
}
roxygen2/man/update_collate.Rd 0000644 0001762 0000144 00000003305 14525717717 016077 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/collate.R
\name{update_collate}
\alias{update_collate}
\alias{@include}
\title{Update Collate field in DESCRIPTION}
\usage{
update_collate(base_path)
}
\arguments{
\item{base_path}{Path to package directory.}
}
\description{
By default, R loads files in alphabetical order. Unfortunately not every
alphabet puts letters in the same order, so you can't rely on alphabetic
ordering if you need one file loaded before another. (This usually doesn't
matter but is important for S4, where you need to make sure that classes are
loaded before subclasses and generics are defined before methods.).
You can override the default alphabetical ordering with \verb{@include before.R},
which specify that \code{before.R} must be loaded before the current file.
Generally, you will not need to run this function yourself; it should be
run automatically by any package that needs to load your R files in
collation order.
}
\section{Collate}{
This is not a roclet because roclets need the values of objects in a package,
and those values can not be generated unless you've sourced the files,
and you can't source the files unless you know the correct order.
If there are no \verb{@include} tags, roxygen2 will leave collate as is.
This makes it easier to use roxygen2 with an existing collate directive,
but if you remove all your \verb{@include} tags, you'll need to also
manually delete the collate field.
}
\examples{
#' If `example-a.R', `example-b.R' and `example-c.R' live in R/
#' and we're in `example-a.R`, then the following @include statement
#' ensures that example-b and example-c are sourced before example-a.
#' @include example-b.R example-c.R
NULL
}
roxygen2/man/rd_roclet.Rd 0000644 0001762 0000144 00000001711 14525717717 015066 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/rd.R
\name{rd_roclet}
\alias{rd_roclet}
\title{Roclet: make Rd files}
\usage{
rd_roclet()
}
\description{
This roclet is the workhorse of roxygen2, producing the \code{.Rd} files that
R uses to document functions, datasets, packages, classes, and more.
See \code{vignette("rd")} for details.
Generally you will not call this function directly
but will instead use \code{\link[=roxygenise]{roxygenise()}} specifying the rd roclet.
}
\examples{
#' The length of a string (in characters)
#'
#' @param x A character vector.
#' @returns An integer vector the same length as `x`.
#' `NA` strings have `NA` length.
#' @seealso [nchar()]
#' @export
#' @examples
#' str_length(letters)
#' str_length(c("i", "like", "programming", NA))
str_length <- function(x) {
}
}
\seealso{
\link{tags-rd}, \link{tags-rd-other}, \link{tags-reuse}, \link{tags-index-crossref} for
tags provided by this roclet.
}
roxygen2/man/namespace_roclet.Rd 0000644 0001762 0000144 00000002175 14525717717 016422 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/namespace.R
\name{namespace_roclet}
\alias{namespace_roclet}
\title{Roclet: make \code{NAMESPACE}}
\usage{
namespace_roclet()
}
\description{
This roclet automates the production of a \code{NAMESPACE} file, which controls
the functions imported and exported by your package, as described in
\href{https://cran.r-project.org/doc/manuals/r-release/R-exts.html}{Writing R extensions}.
The \code{NAMESPACE} is generated in two passes: the first generates only
import directives (because this can be computed without evaluating package
code), and the second generates everything (after the package has been
loaded).
See \code{vignette("namespace")} for details.
}
\examples{
# The most common namespace tag is @export, which declares that a function
# is part of the external interface of your package
#' @export
foofy <- function(x, y, z) {
}
# You'll also often find global imports living in a file called
# R/{package}-package.R.
#' @importFrom magrittr \%>\%
#' @import rlang
NULL
}
\seealso{
\link{tags-namespace} for tags that generate \code{NAMESPACE} directives.
}
roxygen2/man/tags-rd-formatting.Rd 0000644 0001762 0000144 00000001255 14525717717 016625 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/tag-metadata.R
\name{tags-rd-formatting}
\alias{tags-rd-formatting}
\alias{@md}
\alias{@noMd}
\alias{@section}
\title{Tags related to markdown support}
\usage{
#' @md
#' @noMd
#' @section ${1:section title}:
}
\description{
Learn the full details in \code{vignette('rd-formatting')}.
Other less frequently used tags:
\itemize{
\item \verb{@md}: Force markdown processing for a block.
\item \verb{@noMd}: Suppress markdown processing for a block.
\item \verb{@section $\{1:section title\}: }: Add an arbitrary section to the documentation. Now generally superseded in favour of using a level 1 heading.
}
}
roxygen2/man/roxy_block.Rd 0000644 0001762 0000144 00000003175 14525717717 015272 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/block.R
\name{roxy_block}
\alias{roxy_block}
\alias{block_has_tags}
\alias{block_get_tags}
\alias{block_get_tag}
\alias{block_get_tag_value}
\title{Blocks}
\usage{
roxy_block(tags, file, line, call, object = NULL)
block_has_tags(block, tags)
block_get_tags(block, tags)
block_get_tag(block, tag)
block_get_tag_value(block, tag)
}
\arguments{
\item{tags}{A list of \link{roxy_tag}s.}
\item{file, line}{Location of the \code{call} (i.e. the line after the last
line of the block).}
\item{call}{Expression associated with block.}
\item{object}{Optionally, the object associated with the block, found
by inspecting/evaluating \code{call}.}
\item{block}{A \code{roxy_block} to manipulate.}
\item{tag}{A single tag name.}
}
\description{
A \code{roxy_block} represents a single roxygen2 block.
The \verb{block_*} functions provide a few helpers for common operations:
\itemize{
\item \code{block_has_tag(blocks, tags)}: does \code{block} contain any of these \code{tags}?
\item \code{block_get_tags(block, tags)}: get all instances of \code{tags}
\item \code{block_get_tag(block, tag)}: get single tag. Returns \code{NULL} if 0,
throws warning if more than 1.
\item \code{block_get_tag_value(block, tag)}: gets \code{val} field from single tag.
}
}
\examples{
# The easiest way to see the structure of a roxy_block is to create one
# using parse_text:
text <- "
#' This is a title
#'
#' @param x,y A number
#' @export
f <- function(x, y) x + y
"
# parse_text() returns a list of blocks, so I extract the first
block <- parse_text(text)[[1]]
block
}
\keyword{internal}
roxygen2/man/roxygenize.Rd 0000644 0001762 0000144 00000003236 14264614532 015307 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/roxygenize.R
\name{roxygenize}
\alias{roxygenize}
\alias{roxygenise}
\title{Process a package with the Rd, namespace and collate roclets}
\usage{
roxygenize(package.dir = ".", roclets = NULL, load_code = NULL, clean = FALSE)
roxygenise(package.dir = ".", roclets = NULL, load_code = NULL, clean = FALSE)
}
\arguments{
\item{package.dir}{Location of package top level directory. Default is
working directory.}
\item{roclets}{Character vector of roclet names to use with package.
The default, \code{NULL}, uses the roxygen \code{roclets} option,
which defaults to \code{c("collate", "namespace", "rd")}.}
\item{load_code}{A function used to load all the R code in the package
directory. The default, \code{NULL}, uses the strategy defined by
the \code{load} roxygen option, which defaults to \code{\link[=load_pkgload]{load_pkgload()}}.
See \link{load} for more details.}
\item{clean}{If \code{TRUE}, roxygen will delete all files previously
created by roxygen before running each roclet.}
}
\value{
\code{NULL}
}
\description{
This is the workhorse function that uses roclets, the built-in document
transformation functions, to build all documentation for a package. See
the documentation for the individual roclets, \code{\link[=rd_roclet]{rd_roclet()}},
\code{\link[=namespace_roclet]{namespace_roclet()}}, and for \code{\link[=update_collate]{update_collate()}},
for more details.
}
\details{
Note that roxygen2 is a dynamic documentation system: it works by
inspecting loaded objects in the package. This means that you must
be able to load the package in order to document it: see \link{load} for
details.
}
roxygen2/man/roxygen2-package.Rd 0000644 0001762 0000144 00000002340 14527236502 016244 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/roxygen2-package.R
\docType{package}
\name{roxygen2-package}
\alias{roxygen2}
\alias{roxygen2-package}
\title{roxygen2: In-Line Documentation for R}
\description{
\if{html}{\figure{logo.png}{options: style='float: right' alt='logo' width='120'}}
Generate your Rd documentation, 'NAMESPACE' file, and collation field using specially formatted comments. Writing documentation in-line with code makes it easier to keep your documentation up-to-date as your requirements change. 'roxygen2' is inspired by the 'Doxygen' system for C++.
}
\seealso{
Useful links:
\itemize{
\item \url{https://roxygen2.r-lib.org/}
\item \url{https://github.com/r-lib/roxygen2}
\item Report bugs at \url{https://github.com/r-lib/roxygen2/issues}
}
}
\author{
\strong{Maintainer}: Hadley Wickham \email{hadley@posit.co} (\href{https://orcid.org/0000-0003-4757-117X}{ORCID}) [copyright holder]
Authors:
\itemize{
\item Peter Danenberg \email{pcd@roxygen.org} [copyright holder]
\item Gábor Csárdi \email{csardi.gabor@gmail.com}
\item Manuel Eugster [copyright holder]
}
Other contributors:
\itemize{
\item Posit Software, PBC [copyright holder, funder]
}
}
\keyword{internal}
roxygen2/man/escape_examples.Rd 0000644 0001762 0000144 00000002137 14264537272 016246 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/rd-examples.R
\name{escape_examples}
\alias{escape_examples}
\title{Escape examples}
\usage{
escape_examples(x)
}
\description{
This documentation topic is used primarily for testing and to record
our understanding of the \verb{\\example\{\}} escaping rules.
See \url{https://developer.r-project.org/parseRd.pdf} for the details provided
by R core.
}
\examples{
# In examples we automatically escape Rd comments (\%):
100 \%\% 30
# even if they are in strings
"50\%"
# and \\ and \v inside of strings and symbols
"\\v" # vertical tab
"\\\\"
# but not comments: \l \v
# other string escapes are left as is
"\""
"\n"
# Otherwise, backslashes and parentheses are left as is. This
# means that you need to escape unbalanced parentheses, which typically only
# occur in \dontshow{}:
\dontshow{if (FALSE) \{ }
print("Hello")
\dontshow{ \} }
# You also need to escape backslashes in infix operators and comments
# (this is generally rare)
`\%\\\\\%` <- function(x, y) x + y
10 \%\\\% 20
# \\\\ (renders as two backslashes)
}
\keyword{internal}
roxygen2/man/tags-reuse.Rd 0000644 0001762 0000144 00000006276 14550054451 015166 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/tag-metadata.R
\name{tags-reuse}
\alias{tags-reuse}
\alias{@describeIn}
\alias{@eval}
\alias{@evalRd}
\alias{@includeRmd}
\alias{@inherit}
\alias{@inheritDotParams}
\alias{@inheritParams}
\alias{@inheritSection}
\alias{@order}
\alias{@rdname}
\alias{@template}
\alias{@templateVar}
\title{Tags that help you reuse documentation}
\usage{
#' @describeIn ${1:destination} ${2:description}
#' @eval ${1:r-code}
#' @evalRd ${1:r-code}
#' @includeRmd man/rmd/${1:filename}.Rmd
#' @inherit ${1:source} ${2:components}
#' @inheritDotParams ${1:source} ${2:arg1 arg2 arg3}
#' @inheritParams ${1:source}
#' @inheritSection ${1:source} ${2:section name}
#' @order ${1:number}
#' @rdname ${1:topic-name}
#' @template ${1:path-to-template}
#' @templateVar ${1:name} ${2:value}
}
\description{
Learn the full details in \code{vignette('reuse')}.
Key tags:
\itemize{
\item \verb{@describeIn $\{1:destination\} $\{2:description\}}: Document a function or method in the \code{destination} topic.
\item \verb{@inherit $\{1:source\} $\{2:components\}}: Inherit one or more documentation components from another topic. If \code{components} is omitted, all supported components will be inherited.
Otherwise, specify individual components to inherit by picking one or more of \code{params}, \code{return}, \code{title}, \code{description}, \code{details}, \code{seealso}, \code{sections}, \code{references}, \code{examples}, \code{author}, \code{source}, \code{note}, and \code{format}.
\item \verb{@inheritDotParams $\{1:source\} $\{2:arg1 arg2 arg3\}}: Automatically generate documentation for \code{...} when you're passing dots along to another function.
\item \verb{@inheritParams $\{1:source\}}: Inherit argument documentation from another function. Only inherits documentation for arguments that aren't already documented locally.
\item \verb{@inheritSection $\{1:source\} $\{2:section name\}}: Inherit a specific named section from another topic.
\item \verb{@order $\{1:number\}}: Override the default (lexigraphic) order in which multiple blocks are combined into a single topic.
\item \verb{@rdname $\{1:topic-name\}}: Override the file name of generated \code{.Rd} file. Can be used to combine multiple blocks into a single documentation topic.
}
Other less frequently used tags:
\itemize{
\item \verb{@eval $\{1:r-code\}}: Evaluate arbitrary code in the package namespace and insert the results back into the block. Should return a character vector of lines.
\item \verb{@evalRd $\{1:r-code\}}: Evaluate arbitrary code in the package namespace and insert the results back as into the block. Should return a character vector of lines.
\item \verb{@includeRmd man/rmd/$\{1:filename\}.Rmd}: Insert the contents of an \code{.Rmd} into the current block. Superseded in favour of using a code chunk with a child document.
\item \verb{@template $\{1:path-to-template\}}: Use a roxygen2 template. Now superseded in favour of inline R code.
\item \verb{@templateVar $\{1:name\} $\{2:value\}}: Define variables for use in a roxygen2 template.
}
}
\seealso{
Other documentation tags:
\code{\link{tags-index-crossref}},
\code{\link{tags-rd}},
\code{\link{tags-rd-other}}
}
\concept{documentation tags}
roxygen2/man/tags-namespace.Rd 0000644 0001762 0000144 00000004723 14525717717 016007 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/tag-metadata.R
\name{tags-namespace}
\alias{tags-namespace}
\alias{@evalNamespace}
\alias{@export}
\alias{@exportClass}
\alias{@exportMethod}
\alias{@exportPattern}
\alias{@exportS3Method}
\alias{@import}
\alias{@importClassesFrom}
\alias{@importFrom}
\alias{@importMethodsFrom}
\alias{@rawNamespace}
\alias{@useDynLib}
\title{Tags for managing the \code{NAMESPACE}}
\usage{
#' @evalNamespace ${1:r-code}
#' @export
#' @exportClass ${1:class}
#' @exportMethod ${1:generic}
#' @exportPattern ${1:pattern}
#' @exportS3Method ${1:package}::${2:generic}
#' @import ${1:package}
#' @importClassesFrom ${1:package} ${2:class}
#' @importFrom ${1:package} ${2:function}
#' @importMethodsFrom ${1:package} ${2:generic}
#' @rawNamespace ${1:namespace directives}
#' @useDynLib ${1:package}
}
\description{
Learn the full details in \code{vignette('namespace')}.
Key tags:
\itemize{
\item \verb{@export}: Export this function, method, generic, or class so it's available outside of the package.
\item \verb{@exportS3Method $\{1:package\}::$\{2:generic\}}: Export an S3 method. Only needed when the method is for a generic from a suggested package.
\item \verb{@importFrom $\{1:package\} $\{2:function\}}: Import specific functions from a package.
\item \verb{@useDynLib $\{1:package\}}: Import compiled code from another package.
}
Other less frequently used tags:
\itemize{
\item \verb{@evalNamespace $\{1:r-code\}}: Evaluate arbitrary code in the package namespace and insert the results into the \code{NAMESPACE}. Should return a character vector of directives.
\item \verb{@exportClass $\{1:class\}}: Export an S4 class. For expert use only; in most cases you should use \verb{@export} so roxygen2 can automatically generate the correct directive.
\item \verb{@exportMethod $\{1:generic\}}: Export S4 methods. For expert use only; in most cases you should use \verb{@export} so roxygen2 can automatically generate the correct directive.
\item \verb{@exportPattern $\{1:pattern\}}: Export all objects matching a regular expression.
\item \verb{@import $\{1:package\}}: Import all functions from a package. Use with extreme care.
\item \verb{@importClassesFrom $\{1:package\} $\{2:class\}}: Import S4 classes from another package.
\item \verb{@importMethodsFrom $\{1:package\} $\{2:generic\}}: Import S4 methods from a package.
\item \verb{@rawNamespace $\{1:namespace directives\}}: Insert literal text directly into the \code{NAMESPACE}.
}
}
roxygen2/man/roclet_find.Rd 0000644 0001762 0000144 00000001423 14264614456 015375 0 ustar ligges users % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/roclet.R
\name{roclet_find}
\alias{roclet_find}
\title{Create a roclet from a string.}
\usage{
roclet_find(x)
}
\arguments{
\item{x}{Arbitrary R code evaluated in roxygen2 package.}
}
\description{
This provides a flexible way of specifying a roclet in a string.
}
\examples{
# rd, namespace, and vignette work for backward compatibility
roclet_find("rd")
# But generally you should specify the name of a function that
# returns a roclet
roclet_find("rd_roclet")
# If it lives in another package, you'll need to use ::
roclet_find("roxygen2::rd_roclet")
# If it takes parameters (which no roclet does currently), you'll need
# to call the function
roclet_find("roxygen2::rd_roclet()")
}
\keyword{internal}
roxygen2/man/figures/ 0000755 0001762 0000144 00000000000 14553540041 014247 5 ustar ligges users roxygen2/man/figures/logo.png 0000644 0001762 0000144 00000047346 14520721622 015733 0 ustar ligges users PNG
IHDR ޫh cHRM z&