in9.8.0/x86_64 (64-bit)
locale:
[1] en_AU.UTF-8/en_AU.UTF-8/C/C/en_AU.UTF-8/en_AU.UTF-8
attached base packages:
[1] stats graphics grDevices utils datasets methods base
>
-
Mark Cowl
install.package & all code which has embedded
install.packages calls, are there any other ways?
@Brian, thanks for the pointer to the news article on connections - I did learn
something there
cheers,
Mark
On 06/10/2011, at 3:59 AM, Martin Morgan wrote:
> On 10/05/2011 02:36 AM, Mark Co
sages that are produced by install.packages()
when R libraries are being installed.
So, will it be possible for R CMD INSTALL output be written to stdout in the
future?
kind regards,
Mark
-
Mark Cowley, PhD
Pancreatic Cancer Program | Peter
. Code available if anyone's interested
cheers,
Mark
On 11/10/2011, at 12:23 PM, Simon Urbanek wrote:
>
> On Oct 10, 2011, at 8:48 PM, Mark Cowley wrote:
>
>> Dear list,
>> (this is a follow up from a previous query)
>>
>> Why does R CMD INSTALL write most o
U.UTF-8/en_AU.UTF-8
attached base packages:
[1] tools stats graphics grDevices datasets utils methods
[8] base
other attached packages:
[1] updateR_1.0.4 codetools_0.2-8 devtools_0.4
loaded via a namespace (and not attached):
[1] RCurl_1.
elp();
> }
> }, error = function(ex) {
> print(ex);
> })
>
> That way the URL for the help page remain the same (as long as you
> only run one R session) and the internal web server is up and running
> (no need for help.start()).
>
> My $.02
>
> /Henrik
>
Hi guRus,
i'm running R-2.15.1 and the R CMD CHECK output appears to have changed
substantially, in that instead of pointing me to the offending functions or
files, I get lots of 'call sequence' traces as below.
I've been using R CMD CHECK for years & never seen anything like this before.
This
guilty of not looking beyond the
spotlight of the current package.
kind regards,
Mark
On 21/10/2012, at 1:50 AM, Prof Brian Ripley wrote:
> On Sat, 20 Oct 2012, Mark Cowley wrote:
>
>> Hi guRus,
>
>> i'm running R-2.15.1 and the R CMD CHECK output appears to have