similar to: R 2.9.1 is released

Displaying 20 results from an estimated 20000 matches similar to: "R 2.9.1 is released"

2009 Oct 26
0
R 2.9.0 is released
I've rolled up R-2.10.0.tar.gz some hours ago. This is a development release which contains a number of new features, notably a brand new HTML based dynamic help system. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it from http://cran.r-project.org/src/base/R-2/R-2.10.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to
2009 Oct 26
0
R 2.9.0 is released
I've rolled up R-2.10.0.tar.gz some hours ago. This is a development release which contains a number of new features, notably a brand new HTML based dynamic help system. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it from http://cran.r-project.org/src/base/R-2/R-2.10.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to
2009 Oct 26
0
R 2.10.0 is released
(D'oh. Forgot to change the Subject: line...) I've rolled up R-2.10.0.tar.gz some hours ago. This is a development release which contains a number of new features, notably a brand new HTML based dynamic help system. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it from http://cran.r-project.org/src/base/R-2/R-2.10.0.tar.gz or wait
2009 Oct 26
0
R 2.10.0 is released
(D'oh. Forgot to change the Subject: line...) I've rolled up R-2.10.0.tar.gz some hours ago. This is a development release which contains a number of new features, notably a brand new HTML based dynamic help system. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it from http://cran.r-project.org/src/base/R-2/R-2.10.0.tar.gz or wait
2009 Apr 17
0
R 2.9.0 is released
I've rolled up R-2.9.0.tar.gz a short while ago. This is a development release which contains a number of new features. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it (later today) from http://cran.r-project.org/src/base/R-2/R-2.9.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. In case of impatience, try
2009 Apr 17
0
R 2.9.0 is released
I've rolled up R-2.9.0.tar.gz a short while ago. This is a development release which contains a number of new features. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it (later today) from http://cran.r-project.org/src/base/R-2/R-2.9.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. In case of impatience, try
2009 Jun 20
2
Special characters in Rd example section will cause errors
Hi (Duncan?), The other day I noticed some characters will cause errors in R CMD CHECK because of parse_Rd(), and AFAIK, these chars include '%', '{' and '}'. For example, note the comments in the example section: %~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~% \name{testfun} \Rdversion{1.1} \alias{testfun} \title{ A Test } \description{ A test } \usage{ testfun() } \value{ NULL }
2019 Apr 05
0
Bug in the "reformulate" function in stats package
>>>>> Ben Bolker >>>>> on Thu, 4 Apr 2019 12:46:37 -0400 writes: > Proposed patch Thank you Ben! [the rest is technical nit-picking .. but hopefully interesting to the smart R-devel reader base:] There was a very subtle thinko in your patch which is not easily diagnosed from R's parse_Rd(): Error in
2008 Dec 22
0
R 2.8.1 is released
I've rolled up R-2.8.1.tar.gz a short while ago. This is a maintenance release and fixes a number of mostly minor bugs and platform issues. See the full list of changes below. You can get it (in a short while) from http://cran.r-project.org/src/base/R-2/R-2.8.1.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course.
2008 Dec 22
0
R 2.8.1 is released
I've rolled up R-2.8.1.tar.gz a short while ago. This is a maintenance release and fixes a number of mostly minor bugs and platform issues. See the full list of changes below. You can get it (in a short while) from http://cran.r-project.org/src/base/R-2/R-2.8.1.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course.
2019 Apr 18
0
Bug in the "reformulate" function in stats package
Your file didn't make it through the mailing list (which is quite restrictive about which types/extensions it will take). I appreciate your enthusiasm and persistence for this issue, but I suspect you may have trouble convincing R-core to adopt your changes -- they are "better", "easier", "more intuitive" for you ... but how sure are you they are completely
2009 Apr 07
2
parse_Rd() Version 2 on Japanese Vista 32 (encoding problems)
Hi, I need some help with 2.9.0 parse_Rd() Version 2 changes. I read the .pdf file and some posts on r-help, but after playing with this for several hours, I can't seem to get around this UTF-8 problem. - I'm trying to get rid of some warnings during R CMD Check for R 2.9.0Alpha on Japanese Vista 32 - The same setup on a R 2.9.0Alpha English XP Pro 32 works fine without any
2017 Oct 04
1
R CMD Rd2pdf and macros
No, I do not get the same as you. I have tested with R-devel and R-patched compiled today. When I do R CMD Rd2pdf mpra I get (as reported a few days ago) Hmm ... looks like a package Converting Rd files to LaTeX Error : mpra/man/mpra-package.Rd:6: file './DESCRIPTION' does not exist whereas you (Kurt) reports that this works on zTree. When I do R CMD Rd2pdf mpra/man I get - a
2018 Jun 01
0
user macros with multi-line arguments in Rd (was Re: Rd parser throws error for user macros invoked with empty argument)
Thanks for the report, I am testing a patch that will allow multi-line arguments to user macros. Best Tomas On 05/25/2018 04:45 PM, Georgi Boshnakov wrote: > While on the topic of Rd macro arguments, it seems that if a multiline argument is supplied, the lines after the first are silently ignored: > > f <- tempfile() > mac6 <- "\\newcommand{\\mac6}{mac6: #1}" >
2018 May 25
0
Rd parser throws error for user macros invoked with empty argument
Thanks for the report and the examples - and they do not have to be that verbose, it is enough to just define and use a command, e.g. cat("\\newcommand{\\mac1}{MAC1:#1}\\mac1{}", file=f) rd <- tools::parse_Rd(f) Whenever you get an error message like "Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL'", there is a bug (at least the error message
2018 May 25
2
Rd parser throws error for user macros invoked with empty argument
While on the topic of Rd macro arguments, it seems that if a multiline argument is supplied, the lines after the first are silently ignored: f <- tempfile() mac6 <- "\\newcommand{\\mac6}{mac6: #1}" cat(mac6, "\\mac6{2*3 2+2 sin(pi) }\n", file = f) rd <- tools::parse_Rd(f) > rd mac6: 2*3 --- Georgi Boshnakov -----Original Message----- From: Tomas Kalibera
2009 Oct 30
1
parse_Rd and/or lazyload problem
I'm encountering problems when making lazy-loadable databases of the output from 'parse_Rd'. The lazy-load database is of seemingly limitless size when I try to reload it... Admittedly I am using functions that I'm not really supposed to use, which is why this isn't a bug report, but there does seem to be something strange going on; my code is very similar to code that lives
2011 Apr 12
2
parse_Rd raises error when example section contains a quoted percent character
I was writing Rd documentation for a new package when I came across this issue. Here's the smallest example: > library(tools) > cat("\\examples{x <- '<%=rnorm(1)%>'}\n",file=file.path(tempdir(),'test.Rd')) > readLines(file.path(tempdir(),'test.Rd')) [1] "\\examples{x <- '<%=rnorm(1)%>'}" >
2017 Oct 03
2
R CMD Rd2pdf and macros
When I run R CMD Rd2pdf on the man pages of a package, ie R CMD Rd2pdf man I get Converting Rd files to LaTeX Warning in parse_Rd("man/mpra-package.Rd", encoding = "unknown", fragment = FALSE, : man/mpra-package.Rd:6: unknown macro '\packageTitle' Warning in parse_Rd("man/mpra-package.Rd", encoding = "unknown", fragment = FALSE, :
2018 May 14
3
Rd parser throws error for user macros invoked with empty argument
Bug or feature? I get the following error from parse_Rd() when a user Rd macro (including system ones) is invoked with empty argument {}, eg \mymacro{}: Error in tools::parse_Rd(fn) : Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL' A full example is further below with the system macro \CRANpkg{}. In this example it doesn't make sense to use empty argument but