similar to: Two minor escaping issues using \preformatted{....} in Rd format

Hi R-devels, I noticed that you are working quite actively on the new Rd-parser and have made it the default renderer in R-2.10.0dev. So I would like to come back on an issue I have already raised on this list last November ("Two minor escaping issues using \preformatted{....} in Rd format") My setting has slightly changed as \preformatted, AFAICS is not supported within \describe

Hi, I have found an unwanted feature in the Rd to LaTeX convertion regarding \preformatted inside a \section. I have created an Rd example below, which generates an error in the following 'R CMD check' step * creating aroma.affine-manual.tex ... OK * checking aroma.affine-manual.tex ... ERROR LaTeX errors when creating DVI version. This typically indicates Rd problems. I believe

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

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C3BE9C.3FB5BC1A Content-Type: text/plain; charset="iso-8859-1" There is a small bug in the implementation of \preformatted in R 1.8.0: The closing "\end{verbatim}" needs to be followed by a newline, since my latex

Hi, I have been developing a package in R and have been working on documentation. I have a \details function that contains the following: \details{ some text \preformatted{ [my-section] user = apv host = 127.0.0.1 } } When I run R CMD check I get an error while checking the manual. If I remove: \preformatted{ [my-section] user = apv host = 127.0.0.1 } and replace it with [my-section]

Hi, The "\preformatted" environment in Rd files doesn't seem to escape long sequences of backslashes properly when converted to pdf (LaTeX) documentation. I'm running R version 2.14 (from subversion, revision 57751) on Linux (RHEL). Here's an example from the command line: echo

Dear All, I have the following in a .Rd file: ... human readable (not binary) format. The format itself is like the following: \preformatted{ \# vertex1name vertex2name [optionalWeight] vertex3name [optionalWeight] } Here, the first vertex of an edge is preceded with a pound sign ... and it is fine with R 2.9.2, but fails on R-devel, when building the PDF version

Sorry, for asking the same question again, but I got no reactions the last time. Maybe it was just overseen by the experts. I'm using the xtable function with Sweave and Lyx and I would like to know how to get automatic line breaks for long strings in a column of the table. I've learned from the Lyx wiki that the Latex command \linebreak produces table cells with multiple lines. I tried to

Dear list, I've noticed that, when writing examples in an Rd file, you need to escape the '%' character, even if it is valid R code. I can see maybe this is the intended behaviour, but I found it a bit surprising, and leads to cryptic error messages from 'R CMD check'. The relevant section in the "writing R extensions" manual isn't clear on that point either. To

Hi, I have a couple of webgen textile formatting questions. Please feel free to refer me to a textile mailing list if there is one that is more appropriate than here. First, how can I insert three dashes (---) in a <code> or <pre> block? I want to include a YAML file example, and the yaml document separator is three dashes, but this conflicts with the separator in webgen. Example:

Hi, this is perhaps not so much an issue, but as you are currently working on the Rd parser anyway... When you want to document specific S4 methods for an S4 generic by \S4method{} within a \usage{} environment, and the second (signature_list) argument is "long", be it because you use multiple dispatch, be it because you use long class-names, (or both), one would probably like to be

Dear All, I'm trying to draw a TeX histogram with the following pair of commands, pictex(file = "realhisto.tex") hist(Peaklist$V3,xlab="Height $z/\\ut{mm}$",ylab="Probability density $\\phi{}(z-z_0)/(1/\\ut{mm})$") However, in the resulting file realhisto.tex, I get, for example \put {Height \$z/\ut\{mm\}\$} [lB] <0.00pt,0.00pt> at 136.13 9.17 when

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{

Dear R-devels, We have encountered a problem concerning a dead lock in the dependency graph: We have two packages A1 and A2 where A2 extends A1. We have one package vignette for both packages, but which should be included into package A1. So in the "suggests" field of the DESCRIPTION file of A1 we suggest A2 to be able to produce the vignette at build/install time. On the other hand

Ok, I''m hoping this won''t be a forehead slapper, but take a look at this code: physician.name.sub(/''/, "\\''") I''m trying to substitute a single quote with a backslash and a single quote. This seems pretty simple right? Well, someone kick me and tell me why it''s not :) Here''s what I''m getting if the

How can I get a single backslash in a character string? My goal is to escape dots in a string that will be used as a regular expression. I thought I could do it this way: gsub(".", "\\.", x) Unfortunately, "\\" does not represent a literal backslash as I expected, but rather a pair of backslashes: > "\\." [1] "\\." > "\\" [1]

Hi R-devels, recently, we have seen a new warning by "R CMD check" appearing for the devel-version of our package distrEx available on r-forge, e.g. as *|install.packages("/distrEx/",repos="http://r-forge.r-project.org")|* Here is the warning: %--------------------- [...snip ...] * checking for unstated dependencies in R code ... WARNING .get_S4_methods_list():

I am doing unit-tests for Maruku and every once in a while I run into some doubts. I am posting a lot to the list, but all of these messages should be in-topic (tell me if not). Consider the input: --- `There is a literal backtick (\`) here.` `There is a literal backtick (\\`) here.` ``There is a literal backtick (`) here.`` --- The documentation says that line 2 and 3 are equivalent.

Hi! In the rsync man page under " -8, --8-bit-output", it says: . . . All control characters (but never tabs) are always escaped, regardless of this option's setting. The escape idiom that started in 2.6.7 is to output a literal backslash (\) and a hash (#), followed by exactly 3 octal digits. For example, a newline would output as "\#012". A literal backslash

Hi, I noticed a minor flaw in integrate() from package stats: Taking up arguments lower and upper from integrate(), if (lower == Inf) && (upper == Inf) or if (lower == -Inf) && (upper == -Inf) integrate() calculates the value for (lower==-Inf) && (upper==Inf). Rather, it should return 0. Quick fix: ### old code ### ### [snip] else {