similar to: Rd file processing suggestion - % sign in examples

Hi r-devels, I have two minor problems with special characters in Rd files when used within a \preformatted{} markup command: ------------------------------------------------------ 1. issue: backslash + single brace ------------------------------------------------------ I would like to write "\\\}" to produce \} on output (documenting the need to escape the brace once again before

I have written a function for my 'oce' package that creates a data.frame containing a variable name with a prime in it. (I use prime to indicate coordinate rotation, a reasonably standard convention that motivates the odd variable name.) How can I name that in an Rd file? I tried \code{u'} but R-2.9.0 doesn't like to build my package then, since it thinks I'm opening a

Hi, as far as I understand it, the new R devel feature of processing non-Sweave vignettes will (a) locate any "[.][RrSs](nw|tex)$" or ".Rmd" files, (b) check for a registered vignette engine, (c) process the file using the registered "weave" function, (d) and possibly post process the generated weave artifact (e.g. a *.tex file). I'd like to propose to extend

[Automatic forwarding from R-bugs failed. This message has been manually forwarded.] Hi all! I'm trying to add Thomas Lumley's defmacro() function Lumley T. "Programmer's Niche: Macros in {R}", R News, 2001, Vol 1, No. 3, pp 11--13, \url{http://CRAN.R-project.org/doc/Rnews/} to the gtools package (provided that Thomas gives his OK). And I've encountered an error in

Not paying close attention to detail, I entered the equivalent of pstr<-c("b1=200", "b2=50", "b3=0.3") when what I wanted was pnum<-c(b1=200, b2=50, b3=0.3) There was a list thread in 2010 that shows how to deal with un-named vectors, but the same lapply solution doesn't seem to work here i.e., pnum<-lapply(pstr, as.numeric) or similar vapply

Dear R-devel-list, Since I had no answer on the R-help-list (http://permalink.gmane.org/gmane.comp.lang.r.general/284539) I try to present my trouble on the R-devel-list. I am sure in the past (one year ago) to succeed in putting accentuated characters in the \title tag in a .Rd file. Recently, creating a package, I have NA in the title function instead of the text containing the

Hello, macosx 10.13.6, Rdevel r76458 I'm trying to compile against openblas to reproduce an error on the CRAN check page (my package is clean under winbuilder and all but one of the checks). I've downloaded and installed openblas 0.3.7 but I am not 100% sure that it is being used by R. Using ./configure --with-blas="-lopenblas" Then running R to discover the PID I get:

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

I've noticed a curious interpretation of escaped characters in \examples{} in .Rd files. For example, if I type files <- dir(pattern="\\.txt") at the R prompt, I will get a vector containing all file names in the current directory containing the string ".txt". If I put \examples{ files <- dir(pattern="\\.txt") } in an .Rd file of a package,

Hi, I'm trying to document a data frame in Rd format. The data frame contains a variable called 'Health_Env'. When I create a template for the Rd file using 'prompt()' the variable name is included as-is and when I run R CMD CHECK I get a latex error because latex considers '_' a special character (used for subscripts) which is only allowed in math mode. When I

Dear group, I would like to document more than one function on one help page using the Rd language. I tried something like \value{ \code{foo1} returns a list with components \item{arg1}{Argument 1} \item{arg2}{Argument 2} \code{foo2} returns a list with components \item{arg3}{Argument 3} \item{arg4}{Argument 4} } Unfortunately this makes the text "\code{foo2} returns a list

Here is my interaction with R: > sub(x='>|t|',pattern = '|t',replacement='zz') [1] "zz>|t|" So I say to myself "Clearly the | signs need to be escaped, so let's try this" > sub(x='>|t|',pattern = '\|t',replacement='zz') [1] "zz>|t|" Warning messages: 1: '\|' is an unrecognized escape in a

(emacs newb here) After having made some changes in an \items paragraph of \arguments the lines are no longer nicely wrapped. I was looking for a command to reindent/rewrap/reformat the whole \items paragraph but couldn't find anything. The only way, I found, was to go to the end of the first line, do 'c-j' (or RET) which wraps *this* line nicely, but now there is a hard line-break

The Rd.sty LaTeX package is used when building the R manuals, and by the LaTeX pages produced from the man pages. I have tracked down some problems G?bor Cs?rdi was having recently (see "Re: [R] preformatted and '#' in manual pages" in R-help) to a LaTeX problem, and am trying to work out how to fix it. Specifically, the .Rd file he was using had a structure like \dQuote{

I have a large number of troff help files which are automatically converted to .Rd files. Many of these have examples which contain the printed output of the examples. This makes example(functionname) not work. Is there a way to avoid removing all this output by delimiting it in some way such that the output will not appear in R-ex? Secondly, it would be nice if there was a place where output

I'm a little confused when documenting my code using Imports vs. Depends. If I have an example in my .Rd that uses a library that is listed under Imports, it doesn't work, but if it is listed under Depends, it does. What is the proper way to go about using examples that rely on an Imports? Should I just if(require(somepackage)) in the example? Or is there a more elegant way of doing

Dear R gurus and users, for some functions in some of the many packages available for R, with the current definition of \Header given in Rd.sty, the heading bumps into the surrounding words in documentation printed via LaTeX. To alleviate this minor typographical mishap, I'd like to suggest the change to R/doc/manual/Rd.sty included below as a context diff. With this minor diff applied, the

I am stumped in determining the proper syntax for including displayed S code within an R .Rd documentation file, in places other than \examples{}. I have tried \code{ line 1 line 2 } but the lines get run together. When I terminate the lines by \cr, the "\cr" actually appears in the resulting html file. This is all inside a customized \section{}. On a related note, what is

I have a set of functions that I always load on startup. for example, there is my now infamous "is.defined()" function. I would like to add some documentation for these functions, so that I can do a ?is.defined inside R. The documentation tells me how to mark up Rd files is very good, but I wonder how one installs them for access by the R executable (on OSX for me). Do I drop

Should R/src/library/base/man/Extremes.Rd (where max, min, pmax, pmin are documented) refer to which.min and which.max in the "\seealso" section? e.g. change the \seealso section (line 53) of Extremes.Rd to: \code{\link{range}}, \code{\link{which.min}}, etc.}, [Also, is r-help the right place for suggestions about documentation?] thanks, Stephen Eglen