[Rd] R_BATCHSAVE setting in config.site
Douglas Grove
dgrove at fhcrc.org
Fri Jul 29 19:29:22 CEST 2005
Sorry, forgot to provide system info:
I'm running SuSE 9.3 on an AMD Althon4000
platform i686-pc-linux-gnu
arch i686
os linux-gnu
system i686, linux-gnu
status Patched
major 2
minor 1.1
year 2005
month 07
day 29
language R
Doug
On Fri, 29 Jul 2005, Douglas Grove wrote:
> Hi,
>
> I just downloaded and installed last nights version of R-patched
> and decided that I'd set R_BATCHSAVE=--no-save in config.site,
> which I haven't done before.
>
> Since the comment above R_BATCHSAVE in config.site says:
> ## The default behavior of R if it encounters EOF in batch mode.
> ## Set this to one of '--save' or '--no-save' depending whether you
> ## want automatic saving of '.RData' or not.
> so I assumed it should only affect BATCH mode. However, I'm finding
> the opposite, it only affects interactive mode, and *not* BATCH mode.
>
> I configured and made R two different ways, one with R_BATCHSAVE set
> to --no-save and one with it left unset (defaulting to --save).
> I compared the resulting scripts to one another. I found that
> there was no difference in the ${R_HOME}/bin/BATCH scripts but there was
> a difference in the ${R_HOME}/bin/R scripts. When I set R_BATCHSAVE
> to --no-save I got:
> exec "${R_binary}" --no-save ${args}
> rather instead of:
> exec "${R_binary}" ${args}
> one line 175 of /bin/R.
>
> Am I missing something (certainly not an uncommon occurrance) or
> is this a mistake?
>
> Thanks,
> Doug Grove
>
> Statistical Research Associate
> Fred Hutchinson Cancer Center
> Seattle, WA
>
More information about the R-devel
mailing list