\HeaderA{commandArgs}{Extract Command Line Arguments}{commandArgs}
\keyword{environment}{commandArgs}
\keyword{sysdata}{commandArgs}
\keyword{programming}{commandArgs}
\begin{Description}\relax
Provides access to a copy of the command line arguments supplied when
this \R{} session was invoked.
\end{Description}
\begin{Usage}
\begin{verbatim}
commandArgs(trailingOnly = FALSE)
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{trailingOnly}] logical.  Should only arguments after
\code{--args} be returned?
\end{ldescription}
\end{Arguments}
\begin{Details}\relax
These arguments are captured before the standard \R{} command line
processing takes place.  This means that they are the unmodified
values.  This is especially useful with the \code{--args}
command-line flag to \R, as all of the command line after that flag
is skipped.
\end{Details}
\begin{Value}
A character vector containing the name of the executable and the
user-supplied command line arguments.  The first element is the name
of the executable by which \R{} was invoked.  The exact form of this
element is platform dependent: it may be the fully qualified name, or
simply the last component (or basename) of the application, or for an
embedded \R{} it can be anything the programmer supplied.

If \code{trailingOnly = TRUE}, a character vector of those arguments
(if any) supplied after \code{--args}.
\end{Value}
\begin{SeeAlso}\relax
\code{\LinkA{Startup}{Startup}}
\code{\LinkA{BATCH}{BATCH}}
\end{SeeAlso}
\begin{Examples}
\begin{ExampleCode}
commandArgs()
## Spawn a copy of this application as it was invoked,
## subject to shell quoting issues
## system(paste(commandArgs(), collapse=" "))
\end{ExampleCode}
\end{Examples}

