Simon Urbanek wrote:
> On Jun 8, 2006, at 9:08 PM, Herve Pages wrote:
>
>> Man page for 'install.packages' says that if the 'lib' arg is missing,
>> then it "defaults to '.libPaths()[1]' with a warning".
>
> Where are you quoting from? I read (R 2.3.1):
Hi Simon,
I was quoting from the descriptio
Herve,
On Jun 8, 2006, at 9:08 PM, Herve Pages wrote:
> Man page for 'install.packages' says that if the 'lib' arg is missing,
> then it "defaults to '.libPaths()[1]' with a warning".
Where are you quoting from? I read (R 2.3.1):
install.packages can be used to install new packages/bundles. It
Prof Brian Ripley wrote:
> On Thu, 8 Jun 2006, Herve Pages wrote:
>
>> Man page for 'install.packages' says that if the 'lib' arg is missing,
>> then it "defaults to '.libPaths()[1]' with a warning".
>> But, given the 'install.packages' source code, it seems that this
>> warning
>> is issued only
On Thu, 8 Jun 2006, Herve Pages wrote:
> Hello,
>
> Man page for 'install.packages' says that if the 'lib' arg is missing,
> then it "defaults to '.libPaths()[1]' with a warning".
> But, given the 'install.packages' source code, it seems that this warning
> is issued only when 'length(.libPaths())
Hello,
Man page for 'install.packages' says that if the 'lib' arg is missing,
then it "defaults to '.libPaths()[1]' with a warning".
But, given the 'install.packages' source code, it seems that this warning
is issued only when 'length(.libPaths()) > 1'.
So typically, this warning will appear on Ma
