| Line 1... |
Line 1... |
| 1 |
% File src/library/base/man/files.Rd
|
1 |
% File src/library/base/man/files.Rd
|
| 2 |
% Part of the R package, http://www.R-project.org
|
2 |
% Part of the R package, http://www.R-project.org
|
| 3 |
% Copyright 1995-2012 R Core Team
|
3 |
% Copyright 1995-2013 R Core Team
|
| 4 |
% Distributed under GPL 2 or later
|
4 |
% Distributed under GPL 2 or later
|
| 5 |
|
5 |
|
| 6 |
\name{files}
|
6 |
\name{files}
|
| 7 |
\alias{files}
|
7 |
\alias{files}
|
| 8 |
\alias{file.append}
|
8 |
\alias{file.append}
|
| Line 41... |
Line 41... |
| 41 |
#endif
|
41 |
#endif
|
| 42 |
\code{to} can alternatively be the path to a single existing directory.}
|
42 |
\code{to} can alternatively be the path to a single existing directory.}
|
| 43 |
\item{overwrite}{logical; should existing destination files be overwritten?}
|
43 |
\item{overwrite}{logical; should existing destination files be overwritten?}
|
| 44 |
\item{showWarnings}{logical; should the warnings on failure be shown?}
|
44 |
\item{showWarnings}{logical; should the warnings on failure be shown?}
|
| 45 |
\item{recursive}{logical. If \code{to} is a directory, should
|
45 |
\item{recursive}{logical. If \code{to} is a directory, should
|
| 46 |
directories in \code{from} be copied (and their contents)?}
|
46 |
directories in \code{from} be copied (and their contents)? (Like
|
| - |
|
47 |
\command{cp -R} on POSIX OSes.)}
|
| 47 |
\item{copy.mode}{logical: should file permission bits be copied where
|
48 |
\item{copy.mode}{logical: should file permission bits be copied where
|
| 48 |
possible? This applies to both files and directories.}
|
49 |
possible? This applies to both files and directories.}
|
| 49 |
}
|
50 |
}
|
| 50 |
\description{
|
51 |
\description{
|
| 51 |
These functions provide a low-level interface to the computer's
|
52 |
These functions provide a low-level interface to the computer's
|
| Line 106... |
Line 107... |
| 106 |
\code{to} argument can specify a single existing directory. If
|
107 |
\code{to} argument can specify a single existing directory. If
|
| 107 |
\code{copy.mode = TRUE} (added in \R 2.13.0) file read/write/execute
|
108 |
\code{copy.mode = TRUE} (added in \R 2.13.0) file read/write/execute
|
| 108 |
permissions are copied where possible, restricted by
|
109 |
permissions are copied where possible, restricted by
|
| 109 |
\sQuote{\link{umask}}. Other security attributes such as ACLs are not
|
110 |
\sQuote{\link{umask}}. Other security attributes such as ACLs are not
|
| 110 |
copied. On a POSIX filesystem the targets of symbolic links will be
|
111 |
copied. On a POSIX filesystem the targets of symbolic links will be
|
| 111 |
copied rather than the links themselves.
|
112 |
copied rather than the links themselves, and hard links are copied
|
| - |
|
113 |
separately.
|
| 112 |
|
114 |
|
| 113 |
\code{file.symlink} and \code{file.link} make symbolic and hard links
|
115 |
\code{file.symlink} and \code{file.link} make symbolic and hard links
|
| 114 |
on those file systems which support them. For \code{file.symlink} the
|
116 |
on those file systems which support them. For \code{file.symlink} the
|
| 115 |
\code{to} argument can specify a single existing directory. (Unix and
|
117 |
\code{to} argument can specify a single existing directory. (Unix and
|
| 116 |
OS X native filesystems support both. Windows has hard links to
|
118 |
OS X native filesystems support both. Windows has hard links to
|
The R Project SVN
R