--nsize and --vsize

Kurt Hornik Kurt.Hornik@ci.tuwien.ac.at
Tue, 13 Apr 1999 12:14:26 +0200 (CEST)

>>>>> Peter Dalgaard BSA writes:

> Prof Brian D Ripley <ripley@stats.ox.ac.uk> writes:
>> Allows --nsize and --vsize to override these.
>> Retains the previous minimum settings (200k and 2M) but if the user sets
>> nothing uses 250K and 6M.  (Those just about allow MASS+lme to be
>> loaded.)
> ...
>> The only snag I see is that there is no way to change this on an
>> installation-wide basis except to edit bin/R or include/Defn.h
>> and re-compile, but I guess that (especially the first) is safe enough.

> Isn't that essentially the original purpose of using a shell script
> (Win/Mac notwithstanding)? If we want it even easier, we could have
> bin/R doing something like

> ...
> $R_ENV=${R_ENV:-$RHOME/site/Renviron.sh}
> [ -x $R_ENV ] && source $R_ENV
> $R_NSIZE=${R_NSIZE:-250K}
> ...

Something like that, similar to forthcoming R `rc' files (now profile):

	system rc from R_HOME/VERSION/...
	site rc from R_HOME/site/.../Rrc
	user rc from ./.Rrc or ~/.Rrc

	system environ from R_HOME/VERSION/...
	site environ from R_HOME/site/.../Renviron
	user environ from ./.Renviron or ~/.Renviron

Of course, then we'd need options


and I think I'd maybe want (for 1.0)

	--no-user-file => --no-user-rc
	--no-site-file => --no-site-rc

or (maybe better) keep what we have and interpret it as `files' so that
neither rc no env file would be used.


Btw, I'd use `-r' ...

r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch