Hello,
I wish to offer users of my BrailleR package the ability to save their
preferences, which may change by the workspace.
I've toyed with the ideas:
1.saving a file in the corresponding folder; or,
2. creating an object containing all the settings in the workspace
In eithe
On 12 December 2015 at 18:57, Uwe Ligges wrote:
| CRAN has different approaches.
|
| Under Windows, I typically have an R process that controls the check
| process and writes out the process id and timestamp and then starts R
| CMD check. Another watcher simply kills the process of a given proc
On 12.12.2015 17:34, Dirk Eddelbuettel wrote:
On 12 December 2015 at 11:00, Duncan Murdoch wrote:
| On 12/12/2015 9:30 AM, Dirk Eddelbuettel wrote:
| >
| > For Rcpp and friends, I frequently run 'R CMD check' in "batch mode" over a
| > large set of packages. That works fine, apart from taking
On 12 December 2015 at 11:36, Paul Gilbert wrote:
|
|
| On 12/12/2015 11:00 AM, Duncan Murdoch wrote:
| > On 12/12/2015 9:30 AM, Dirk Eddelbuettel wrote:
| >>
| >> For Rcpp and friends, I frequently run 'R CMD check' in "batch mode"
| >> over a
| >> large set of packages. That works fine, apart
On 12/12/2015 11:00 AM, Duncan Murdoch wrote:
On 12/12/2015 9:30 AM, Dirk Eddelbuettel wrote:
For Rcpp and friends, I frequently run 'R CMD check' in "batch mode"
over a
large set of packages. That works fine, apart from taking long :)
I am using the exact same script (which is home-grown a
On 12 December 2015 at 11:00, Duncan Murdoch wrote:
| On 12/12/2015 9:30 AM, Dirk Eddelbuettel wrote:
| >
| > For Rcpp and friends, I frequently run 'R CMD check' in "batch mode" over a
| > large set of packages. That works fine, apart from taking long :)
| >
| > I am using the exact same script
On 12/12/2015 9:30 AM, Dirk Eddelbuettel wrote:
For Rcpp and friends, I frequently run 'R CMD check' in "batch mode" over a
large set of packages. That works fine, apart from taking long :)
I am using the exact same script (which is home-grown and could do with a
revision, but is public at [1]
For Rcpp and friends, I frequently run 'R CMD check' in "batch mode" over a
large set of packages. That works fine, apart from taking long :)
I am using the exact same script (which is home-grown and could do with a
revision, but is public at [1] -- basically just a big loop over a set of
packag
