rcmd_safe_env

It currently has the following variables:<ul>
<li><code>CYGWIN="nodosfilewarning"</code>: On Windows, do not warn about MS-DOS
style file names.</li>
<li><code>R_TESTS=""</code> This variable is set by <code>R CMD check</code>, and makes the
child R process load a startup file at startup, from the current
working directory, that is assumed to be the <code>/test</code> directory
of the package being checked. If the current working directory is
changed to something else (as it typically is by <code>testthat</code>, then R
cannot start. Setting it to the empty string ensures that <code>callr</code> can
be used from unit tests.</li>
<li><code>R_BROWSER="false"</code>: typically we don't want to start up a browser
from the child R process.</li>
<li><code>R_PDFVIEWER="false"</code>: similarly for the PDF viewer.</li>
</ul>

It is sometimes useful to perform a computation in a separate
R process, without affecting the current R process at all.  This
packages does exactly that.

Gabor Csardi

callr

Call R from R

Gábor Csárdi

Winston Chang

Posit Software, PBC 

Ascent Digital Services 

rcmd_safe_env function

rcmd_safe_env returns a set of environment variables that are
more appropriate for rcmd_safe(). It is exported to allow manipulating
these variables (e.g. add an extra one), before passing them to the
rcmd() functions. — rcmd_safe_env

<code>rcmd_safe_env</code> returns a set of environment variables that are
more appropriate for <code>rcmd_safe()</code>. It is exported to allow manipulating
these variables (e.g. add an extra one), before passing them to the
<code>rcmd()</code> functions.

rcmd_safe_env: `rcmd_safe_env` returns a set of environment variables that are more appropriate for `rcmd_safe()`. It is exported to allow manipulating these variables (e.g. add an extra one), before passing them to the `rcmd()` functions.

Description

Usage

Arguments

Value

Details