> From: Simon Urbanek
> By default there is no column name for a column of row names.
> spreadsheets. Note that such CSV files can be read in R by
>
>read.csv(file = "", row.names = 1)
AHA!! Many thanks.
I see this clue is in ?write.table, though; I was looking for help on
> the "unhelpful" column are the row names. They are considered an
> important part of a data frame and therefore the default (row.names =
> TRUE) is to not lose them (as there is no way back once you do). If you don't
> want to preserve the row names you can simply set row.names=FALSE.
Please run
Apologies if this is a well-worn question; I haven’t found it so far but
there's a lot of r-dev and I may have missed it in the archives. In the mean
time:
I've managed to avoid writing csv files with R for a couple of decades but
we're swopping data with a collaborator and I've tripped over an
Note that in
> > quantile(c("1","2","3"),p=.5)
> Error in (1 - h) * qs[i] :
> argument non numérique pour un opérateur binaire
the default quantile type (7) does not work for non-numerics.
Quantile types 1 and 3 work as expected:
> quantile(c("1","2","3"),p=.5, type=1)
50%
"2"
> quantile(c(
> From: William Dunlap [mailto:wdun...@tibco.com]
> Precedence is a property of the parser and has nothing to do with the
> semantics assigned to various symbols.
Yes, but output depends on evaluation as well as precedence. Seeing different
things wasn't an immediate surprise.
Your own parse(
> From: R-devel [mailto:r-devel-boun...@r-project.org] On Behalf Of Ant F
> Sent: 29 August 2019 12:06
> To: r-devel@r-project.org
> Subject: [Rd] ?Syntax wrong about `?`'s precedence ?
> ...
> See the following example :
>
> `?` <- `+`
I'm curious; What did you expect to happen if you replac
To throw a very small pennyworth into this debate, the metRology package I
maintain uses mixed case to highlight R for that community when I'm talking
about, or citing it. R takeup in that community is not yet high and the visible
reminder seems to help.
I'll obviously accept a consensus deci
> It is pure native R annotation, I mean à la java. I wish to have an @
> operator available a R language level to create/embed real code
> annotations. Currently, the best I can get is to use a trick of hiding such
> thing behind a comment. Neither good, not the right way, as comments are
> commen
Please forgive the unorthodox posting, but some marketing genius here has
decided I need a new corporate email address and has duly changed my outgoing
email without adequate notice to amend listserve subscriptions. The result is a
lot of unexpected bounces from R-help and R-devel. I'll try to f
Is there a quick way of checking the R manuals built from the .texi files in
../doc/manual without building the rest of R?
Going from a vanilla checkout, some included files are missing (eg
version.texi) and created by the makefiles, so it looks like the complete make
script needs to be run at
I'm sure i've seen the answer to this, but can't find it:
If there is executable code in an R package .R file that does not return a
function (that is, something like x <- rnorm(5), outside any function body ),
what will actually happens at build and load time?
And (more importantly, so I can p
11 matches
Mail list logo
