track.start(..., auto = TRUE). This function differs from track.rescan() in that
track.rescan() updates R view of the database to agree with
changes on disk, while track.sync() is primarily intended to
go the other way (to make the disk database agree with R).
track.sync(pos = 1, master=c("auto", "envir", "files"), envir = as.environment(pos),
trackingEnv = getTrackingEnv(envir), full = TRUE,
dryRun = FALSE, taskEnd = FALSE)auto will
default to "files" (the only sensible interpretation).
Otherwise, must be supplied (to avoid accidents witpos=)
of specifying the environment being tracked, but should be rarely needed.TRUE, do a full check, which involves
checking that all apparently tracked variables do in fact have an
active binding. If NA, only do a full check if more than
track.options("autoTrackFullSyncWait") TRUE, no changes are made to either the file
system or to the R environment, but changes that would be made are
printed out. Note that a change to a file for a tracked variable
will not be detect.TRUE when called at the end of a
top-level command task (i.e., when called by the task callback
handler.) Currently, this function will not correctly handle the case where
master="files" and where objects are cached and an underlying
file is changed.
track.rescan for rescanning a tracked database
after the files on disk have changed (this is usually only used for
tracked environment attached at a position 2 or greater.)