On Tue, 2005-06-07 at 21:33 -0700, Mike R wrote:
On 6/7/05, Marc Schwartz [EMAIL PROTECTED] wrote:
On 6/7/05, Gabor Grothendieck [EMAIL PROTECTED] wrote:
On 6/7/05, Liaw, Andy [EMAIL PROTECTED] wrote:
snips
Thanks Andy, Gabor and Marc.
contents of .Rprofile
.First -
On 6/8/05, Marc Schwartz [EMAIL PROTECTED] wrote:
snips
Thanks Marc,
Cool ideas, thanks! Building on them, here is a twist.
With this line in .Rprofile:
.First - function() {if(Sys.getenv(R_PROJECT)!=)
source(Sys.getenv(R_PROJECT))}
R can be run with this bash command line:
## export
On Wed, 2005-06-08 at 11:32 -0700, Mike R wrote:
On 6/8/05, Marc Schwartz [EMAIL PROTECTED] wrote:
snips
Thanks Marc,
Cool ideas, thanks! Building on them, here is a twist.
With this line in .Rprofile:
.First - function() {if(Sys.getenv(R_PROJECT)!=)
Hi All,
How does one create an executable R-script, similar
to an executable python script, or shell script except
that when the R-script is finished, the R session remains
open and becomes interactive.
If I do this:
R script.r
then R exits when finished.
On the other hand, starting R
On 6/7/05, Mike R [EMAIL PROTECTED] wrote:
Hi All,
How does one create an executable R-script, similar
to an executable python script, or shell script except
that when the R-script is finished, the R session remains
open and becomes interactive.
If I do this:
R script.r
then R
On Tue, 2005-06-07 at 19:37 -0700, Mike R wrote:
Hi All,
How does one create an executable R-script, similar
to an executable python script, or shell script except
that when the R-script is finished, the R session remains
open and becomes interactive.
If I do this:
R script.r
On 6/7/05, Marc Schwartz [EMAIL PROTECTED] wrote:
On 6/7/05, Gabor Grothendieck [EMAIL PROTECTED] wrote:
On 6/7/05, Liaw, Andy [EMAIL PROTECTED] wrote:
snips
Thanks Andy, Gabor and Marc.
contents of .Rprofile
.First - function() {source(startup.r)}
contents of wrapR.v1
