Dear Andy, Duncan, et al.
Based on comments from Andy and Duncan, I'd like to revise my
proposal as follows:
1. Rename the current "RSiteSearch.function" to
"findFunction" and the package name from "RSiteSearch.function" to
"findFunction", with "findFun" being an alias fo
I'm trying to build an executable for a program I wrote. The
compilation steps go well, but the linking step fails with a libtool
"version mismatch" error. My linking command has this prefix:
/path/to/R/bin/R CMD LINK gcc -g -std=gnu99 ... etc.
The error looks like this:
libtool: Version misma
I am not sure if this is a documentation problem or an implementation
problem:
The 'partial' feature of sort works fine with all values of na.last for some
values of 'partial':
> sort(c(3,NA,1,2),na.last=FALSE,partial=1:2) # find minimum values
[1] NA 1 2 3
> sort(c(3,NA,1,2),na.last=TRUE,
Here's a replacement 'q' function that spits out the path of the
workspace image:
q = function (save = "default", status = 0, runLast = TRUE)
{
cat(paste("Workspace image is
",file.path(getwd(),formals(save.image)$file),'\n'))
flush.console()
.Internal(quit(save, status, runLast))
}
Note the tric
On Jun 5, 2009, at 9:30 AM, nachiket...@cox.net wrote:
> Full_Name: N. Srinivasan
> Version: 2.8.1
> OS: Linux
> Submission from: (NULL) (68.110.225.2)
>
>
> * Installing *source* package 'RODBC' ...
> checking for gcc... gcc -std=gnu99
> checking for C compiler default output file name... a.out
>
Full_Name: N. Srinivasan
Version: 2.8.1
OS: Linux
Submission from: (NULL) (68.110.225.2)
* Installing *source* package 'RODBC' ...
checking for gcc... gcc -std=gnu99
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cros
On Fri, Jun 5, 2009 at 11:52 AM, Barry
Rowlingson wrote:
> On Fri, Jun 5, 2009 at 3:01 PM, Gabor
> Grothendieck wrote:
>
>
>>
>> Save workspace to /home/me/workspace/.RData? [ y(es) / (n(o) /
>> c(ancel) / o(ther) ]:
>
> Quitting emacs produces this:
>
> Save file /foo/bar/baz.qux? (y, n, !, ., q,
On Fri, 5 Jun 2009, Gavin Simpson wrote:
On Fri, 2009-06-05 at 15:42 +0100, Prof Brian Ripley wrote:
Why not use NROW?
No reason - had forgotten this existed.
I was testing NROW after having seen the R-help message, so will go
ahead with that solution. But as I was doing so, something urg
On Fri, Jun 5, 2009 at 3:01 PM, Gabor
Grothendieck wrote:
>
> Save workspace to /home/me/workspace/.RData? [ y(es) / (n(o) /
> c(ancel) / o(ther) ]:
Quitting emacs produces this:
Save file /foo/bar/baz.qux? (y, n, !, ., q, C-r, d or C-h)
I'm not sure what any other than the first two do. I d
On Fri, 2009-06-05 at 15:42 +0100, Prof Brian Ripley wrote:
> Why not use NROW?
No reason - had forgotten this existed.
So here is another patch:
[ga...@desktop ~]$ svn diff ~/R/devel/src/
Index: /home/gavin/R/devel/src/library/stats/R/arima.R
Why not use NROW?
On Fri, 5 Jun 2009, Gavin Simpson wrote:
Dear List,
A posting to R-Help exposed this problem with the print method for
objects of class Arima:
set.seed(1)
x <- arima.sim(n = 100, list(ar = 0.8897, ma = -0.2279))
mod <- arima(x, order = c(1,0,1))
coefs <- coef(mod)
mod2 <- a
Any change here is not so simple to implement as to propose: this is
not something in the R engine, but part of the clean-up action in the
front end. That means that there are at least 3 versions to handle in
the standard front ends (and that for R.app is not in the main source
tarball). And
Dear List,
A posting to R-Help exposed this problem with the print method for
objects of class Arima:
> set.seed(1)
> x <- arima.sim(n = 100, list(ar = 0.8897, ma = -0.2279))
> mod <- arima(x, order = c(1,0,1))
> coefs <- coef(mod)
> mod2 <- arima(x, order = c(1,0,1), fixed = coefs)
> mod2
Call:
On Fri, Jun 5, 2009 at 9:43 AM, Wacek
Kusnierczyk wrote:
> Mathieu Ribatet wrote:
>> I guess that having something like this
>>
>>> q()
>>> Save workspace image (/home/me/workspace/.RData)? [y/n/c/e]:
>>>
>>
>> where "e" means Editing the path should be clear enought, isn't it?
>>
>
> good idea; m
On 6/5/2009 9:46 AM, Barry Rowlingson wrote:
On Fri, Jun 5, 2009 at 1:46 PM, Mathieu Ribatet wrote:
I guess that having something like this
q()
Save workspace image (/home/me/workspace/.RData)? [y/n/c/e]:
where "e" means Editing the path should be clear enought, isn't it?
'e' might be thou
On 6/5/2009 9:41 AM, spencerg wrote:
Liaw, Andy wrote:
From: spencerg
Thank you all for your suggestions. My goal with this
is to make
it as easy as possible for R users to find what they want in
contributed
packages. A referee for our "R Journal" manuscript complained that
"RSit
On Fri, Jun 5, 2009 at 1:46 PM, Mathieu Ribatet wrote:
> I guess that having something like this
>> q()
>> Save workspace image (/home/me/workspace/.RData)? [y/n/c/e]:
>
> where "e" means Editing the path should be clear enought, isn't it?
'e' might be thought to mean 'exit' in English, which mak
Liaw, Andy wrote:
From: spencerg
Thank you all for your suggestions. My goal with this
is to make
it as easy as possible for R users to find what they want in
contributed
packages. A referee for our "R Journal" manuscript complained that
"RSiteSearch.function" was too much to type
I think e is better than others.
Ronggui
2009/6/5 Wacek Kusnierczyk :
> Mathieu Ribatet wrote:
>> I guess that having something like this
>>
>>> q()
>>> Save workspace image (/home/me/workspace/.RData)? [y/n/c/e]:
>>>
>>
>> where "e" means Editing the path should be clear enought, isn't it?
>>
>
Mathieu Ribatet wrote:
> I guess that having something like this
>
>> q()
>> Save workspace image (/home/me/workspace/.RData)? [y/n/c/e]:
>>
>
> where "e" means Editing the path should be clear enought, isn't it?
>
good idea; maybe 'o' for 'other path'; or 'a' for 'alternative path';
I guess that having something like this
> q()
> Save workspace image (/home/me/workspace/.RData)? [y/n/c/e]:
where "e" means Editing the path should be clear enought, isn't it?
Best,
Mathieu
Le vendredi 05 juin 2009 à 14:36 +0200, Wacek Kusnierczyk a écrit :
> Duncan Murdoch wrote:
> > On 05/06/
Duncan Murdoch wrote:
> On 05/06/2009 7:53 AM, Barry Rowlingson wrote:
>> When I quit R, it says:
>>
>> > q()
>> Save workspace image? [y/n/c]:
>>
>> and since I've probably got 3 R sessions running in however many
>> different directories and I might have jumped around with setwd() , I
>> forge
2009/6/5 Duncan Murdoch :
> On 05/06/2009 7:53 AM, Barry Rowlingson wrote:
>>
>> When I quit R, it says:
>>
>> > q()
>> Save workspace image? [y/n/c]:
>>
>> and since I've probably got 3 R sessions running in however many
>> different directories and I might have jumped around with setwd() , I
>
When I quit R, it says:
> q()
Save workspace image? [y/n/c]:
and since I've probably got 3 R sessions running in however many
different directories and I might have jumped around with setwd() , I
forget exactly where R wants to save its workspace image. So could q()
be changed to say what file
On 05/06/2009 7:53 AM, Barry Rowlingson wrote:
When I quit R, it says:
> q()
Save workspace image? [y/n/c]:
and since I've probably got 3 R sessions running in however many
different directories and I might have jumped around with setwd() , I
forget exactly where R wants to save its workspac
Barry Rowlingson wrote:
> Would something like
>
> > q()
> Save workspace image (/home/me/workspace/.RData)? [y/n/c]:
>
> be useful to anyone else? Just thought I'd ask before I dive into
> internals or wrap the q function for myself.
>
yes, it would be very useful to me.
vQ
_
From: spencerg
>
> Thank you all for your suggestions. My goal with this
> is to make
> it as easy as possible for R users to find what they want in
> contributed
> packages. A referee for our "R Journal" manuscript complained that
> "RSiteSearch.function" was too much to type, sugges
27 matches
Mail list logo
