The reason I noticed this is that I do not know how
the screens are numbered.
And for future reference, is there a source that documents
how to create a patch for documentation or source code?
I have never made a patch but I would like to be able
to do this in the future.
Thanks,
Doug
On Tue
On Fri, 9 Sep 2005, Martin Maechler wrote:
> >>>>> "Douglas" == Douglas Grove <[EMAIL PROTECTED]>
> >>>>> on Thu, 8 Sep 2005 15:33:02 -0700 (PDT) writes:
>
> Douglas> Hi,
> Douglas> It would be great if someone
Hi,
It would be great if someone would add write.delim() as an
adjunct to write.table(), just as with write.csv().
I store a lot of data in tab-delimited files and can read
it in easily with: read.delim("text.txt", as.is=TRUE)
and would love to be able to write it out as easily when
I create the
r all, so it's
not a great leap to assume it would be considered a 'batch' mode.
> This setting should probably be described in the R-admin manual, perhaps
> with a better name.
It would be good to mention somewhere (probably in ?quit) that setting
R_SAVEBATCH to --no-save will
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
major2
minor1.1
year 2005
month07
day 29
language R
Doug
On Fri, 29 Jul 2005, Do
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 thi
