Displaying 20 results from an estimated 5000 matches similar to: "New package Rd2roxygen: Convert Rd to roxygen documentation"
2011 Jan 10
0
Package Rd2roxygen v0.1-5
Hi,
A new version (0.1-5) of Rd2roxygen is on CRAN now.
Rd2roxygen is a package to help developers transit from the raw Rd
files to roxygen-style documentations, and it also has utilities to
help build the package (with options to reformat the usage and
examples sections).
Updates:
?o a new way to reformat the usage and examples sections generated by
roxygen; it is more reliable than earlier
2011 Jan 10
0
Package Rd2roxygen v0.1-5
Hi,
A new version (0.1-5) of Rd2roxygen is on CRAN now.
Rd2roxygen is a package to help developers transit from the raw Rd
files to roxygen-style documentations, and it also has utilities to
help build the package (with options to reformat the usage and
examples sections).
Updates:
?o a new way to reformat the usage and examples sections generated by
roxygen; it is more reliable than earlier
2010 Nov 25
3
Go (back) from Rd to roxygen
Hi all,
Since roxygen is a great help to document R packages, I am wondering
if there exists an approach to go back from the raw Rd files to
roxygen-documentation? E.g. turn "\author{Somebody}" into "@author
Somebody". This sounds ridiculous, but I believe it helps in the long
term for me to maintain R packages.
Thanks!
Regards,
Yihui
--
Yihui Xie <xieyihui at
2010 Nov 27
0
How to stop roxygen from creating Rd for functions that are not exported?
Hi all,
It seems roxygen will create Rd files for any functions under the ./R/
directory, and I did not find a way to hide certain functions, even if
I specified a name space. E.g.
#' @export
f = function() {}
#' do nothing
g = function() {}
If I run roxygenize() on the package, both f and g will be documented,
although only f is visible to the users.
Thanks!
Regards,
Yihui
--
Yihui
2011 Apr 14
0
tikzDevice 0.6.0
Cameron and I are pleased to announce version 0.6.0 of the tikzDevice
package which should be available shortly at your local CRAN mirror!
The tikzDevice makes it possible to export R graphics as LaTeX code
that can be included in other documents or compiled into stand alone
figures. The full power of LaTeX is available for typesetting text and
mathematical expressions inside figures produced
2011 Apr 14
0
tikzDevice 0.6.0
Cameron and I are pleased to announce version 0.6.0 of the tikzDevice
package which should be available shortly at your local CRAN mirror!
The tikzDevice makes it possible to export R graphics as LaTeX code
that can be included in other documents or compiled into stand alone
figures. The full power of LaTeX is available for typesetting text and
mathematical expressions inside figures produced
2013 Jan 04
1
Bug in R CMD check for \ in Rd?
Hi,
I have a function knit_expand() and its source/Rd are below:
https://github.com/yihui/knitr/blob/master/R/template.R#L43-L44
https://github.com/yihui/knitr/blob/master/man/knit_expand.Rd
When I run R CMD check on the package I get this warning (with both R
2.15.2 and R-devel):
* checking for code/documentation mismatches ... WARNING
Codoc mismatches from documentation object
2010 Sep 18
1
Check for updates under Windows (Was: a reliable way to check the latest version of R on CRAN?)
Dear R developers,
I asked this question in r-help list but have not got a definite
solution yet, and I think it might be more appropriate to ask
developers or CRAN maintainers directly. Many software packages often
have a menu item like "Check for updates" under the "Help" menu, e.g.
Filezilla and Firefox, and I believe it is also necessary for R (at
least for R GUI under
2011 Oct 17
1
What does \Sexpr[results=rd]{} exactly mean in Rd?
Hi,
I have spent a few hours on the R-exts manual and the documentation of
parse_Rd() (as well as the PDF document in the references), but I
still have not figured out what results=rd means. I thought I could
use an R code fragment to create an Rd fragment dynamically. Here is
an example, in which I was expected the output to be a describe list
<DL> in HTML, but it turns out not to be true.
2013 Mar 09
1
Why cannot `Rscript -e` accept an empty line?
See the example below (under Ubuntu):
$ Rscript -e '1' -e '2'
[1] 1
[1] 2
$ Rscript -e '1' -e '' -e '2'
ERROR: option '-e' requires an argument
$ uname -a
Linux xie 3.5.0-25-generic #39-Ubuntu SMP Mon Feb 25 18:26:58 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
Similar problem under Windows:
Rscript -e "1" -e "" -e "2"
[1]
2011 Mar 05
1
file mode lost in file.copy()?
Hi,
Recently I noticed file.copy() would discard the file mode
information. Is this the expected behaviour or a bug for file.copy()?
> file.create('testfile')
[1] TRUE
> file.info('testfile')
size isdir mode mtime ctime
testfile 0 FALSE 644 2011-03-05 17:06:39 2011-03-05 17:06:39
atime uid gid uname grname
2011 Mar 05
1
file mode lost in file.copy()?
Hi,
Recently I noticed file.copy() would discard the file mode
information. Is this the expected behaviour or a bug for file.copy()?
> file.create('testfile')
[1] TRUE
> file.info('testfile')
size isdir mode mtime ctime
testfile 0 FALSE 644 2011-03-05 17:06:39 2011-03-05 17:06:39
atime uid gid uname grname
2011 Jan 05
2
convert expressions to characters
Hi,
Suppose I have
x = parse(text = "
{y=50+50+50#'asfasf'
}
")
now x is an expression with some src attributes.
> x
expression({y=50+50+50#'asfasf'
})
attr(,"srcfile")
<text>
attr(,"wholeSrcref")
{y=50+50+50#'asfasf'
}
My question is, how can I get my string back (the string passed to
parse() as the text argument)?
>
2013 Apr 08
2
savePlot() under Windows
Hi,
A Windows user asked me a question and I believe this is a bug of R
3.0.0 under Windows:
> plot(1:10)
> savePlot('test.wmf')
Error in .External(C_savePlot, device, filename, type, restoreConsole) :
Incorrect number of arguments (4), expecting 3 for 'savePlot'
> sessionInfo()
R version 3.0.0 (2013-04-03)
Platform: x86_64-w64-mingw32/x64 (64-bit)
locale:
[1]
2011 Apr 10
1
deparse operators in expressions
Hi,
I observed a slight problem in deparse(): it will add spaces around
most operators except /. I wonder if this is easy to fix. I know this
is quite trivial, but I will appreciate if / is not treated as an
exception. Examples:
> deparse(expression(1/1))
[1] "expression(1/1)"
> deparse(expression(1+1))
[1] "expression(1 + 1)"
> deparse(expression(1%in%1))
[1]
2011 Jun 20
1
Quote the path of graphics output in Sweave when it contains spaces
Hi,
I'm aware of the definition of a "valid filename" in
.SweaveValidFilenameRegexp, but I think it might be better to quote
the filename when it contains spaces instead of just giving a warning.
This should bring us safer LaTeX code (although I never use spaces in
paths).
Here is the simple patch:
Index: src/library/utils/R/SweaveDrivers.R
2013 Feb 19
0
knitr version 1.1
Hi,
I released knitr 1.1 to CRAN a few days ago:
http://cran.r-project.org/package=knitr See all new features and
changes at https://github.com/yihui/knitr/blob/master/NEWS.md#changes-in-knitr-version-11
The version 1.0 does not imply perfect stability or maturity. The
major version number was bumped from 0.x to 1.x due to a number of
important features and the breaking of compatibility with
2013 Feb 19
0
knitr version 1.1
Hi,
I released knitr 1.1 to CRAN a few days ago:
http://cran.r-project.org/package=knitr See all new features and
changes at https://github.com/yihui/knitr/blob/master/NEWS.md#changes-in-knitr-version-11
The version 1.0 does not imply perfect stability or maturity. The
major version number was bumped from 0.x to 1.x due to a number of
important features and the breaking of compatibility with
2012 May 02
0
New version of the knitr package (0.5)
The knitr package version 0.5 is on CRAN now. It has gone through
extensive development in the past few months, and about 200 issues
were solved (https://github.com/yihui/knitr/issues) thanks to the
feedback of users, which greatly improved the quality and usefulness
of this package. For a complete list of changes, see
https://github.com/yihui/knitr/blob/master/NEWS
Most notable new features are:
2012 May 02
0
New version of the knitr package (0.5)
The knitr package version 0.5 is on CRAN now. It has gone through
extensive development in the past few months, and about 200 issues
were solved (https://github.com/yihui/knitr/issues) thanks to the
feedback of users, which greatly improved the quality and usefulness
of this package. For a complete list of changes, see
https://github.com/yihui/knitr/blob/master/NEWS
Most notable new features are: