compileKnitr.default

compileKnitr

The filename and (optional) path of the
     document to be compiled.

filename, path

Additional arguments passed to <code><a href="/link/compileLaTeX?package=R.rsp&version=0.15.0" rd-options="" data-mini-rdoc="R.rsp::compileLaTeX">compileLaTeX</a></code>().

outPath

If <code><a href="/link/TRUE?package=R.rsp&version=0.15.0&to=base%3Alogical" rd-options="base:logical" data-mini-rdoc="base:logical::TRUE">TRUE</a></code>, and a postprocessing method exists for
     the generated product, it is postprocessed as well.

postprocess

See <code><a href="/link/Verbose?package=R.rsp&version=0.15.0&to=R.utils" rd-options="R.utils" data-mini-rdoc="R.utils::Verbose">Verbose</a></code>.

verbose

internal

file

The RSP markup language makes any text-based document come alive.  RSP provides a powerful markup for controlling the content and output of LaTeX, HTML, Markdown, AsciiDoc, Sweave and knitr documents (and more), e.g. 'Today's date is <%=Sys.Date()%>'.  Contrary to many other literate programming languages, with RSP it is straightforward to loop over mixtures of code and text sections, e.g. in month-by-month summaries.  RSP has also several preprocessing directives for incorporating static and dynamic contents of external files (local or online) among other things.  Functions rstring() and rcat() make it easy to process RSP strings, while rfile() compiles RSP files (also online) into their final outputs, e.g. rfile('report.tex.rsp') generates 'report.pdf'.  RSP is ideal for self-contained scientific reports and R package vignettes.

compileKnitr: Compiles a Knitr file

Description

Usage

Arguments

Value

See Also