similar to: Rd.sty question: LaTeX expert needed

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

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

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]

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

IMHO trailing spaces should be permitted in POD files. Currently they are prevented by the git upload hook. The reason to allow them in POD files is because indentation is used to indicate blocks of preformatted text (the equivalent of <pre> in HTML). To keep code together in the output if it contains blank lines you have to add a line containing a single space. For an example of where

I am writing course notes in LaTeX. In the part where I am describing model-fitting functions in R I want to use a ~ character inline. If I am displaying an example of R code in its own environment I use the alltt environment, which protects the ~ character. I have forgotten how to protect the ~ when I am writing something like The operator `~' is used to define a model formula in \R.

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 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

Hi, Due to a change in Rd.sty a few days ago (https://github.com/wch/r-source/commit/620eb9a#diff-3bf3d821c6faae50cd6ec931f6f63296L272), the default installation of TeXLive 2009 or 2012 no longer works when building Rd to PDF. The error log is like this: =============== Converting Rd files to LaTeX ..... Creating pdf output from LaTeX ... Error in texi2dvi(file = file, pdf = TRUE, clean = clean,

Just wondering if this is the expected behaviour. I was wanting to produce quoted text within \code{}, without manually entering the '"'. \dQuote{} seems advisable after reading the Writing R Extensions manual, so I tried \code{\dQuote{mytext}} expecting it to produce "mytext" in monospace font (with ' ' round it in the R help files) but it appears that

HPUX doesn't seem to ship with a set of troff macros that can handle the OpenSSH manpages. Maybe other OSs have this problem? Rather than sodding about with the tmac/ directory, I think we should do one of two things: 1. Ship a set of preformatted manpages, and either auto-install them in $prefix/man/cat{1,1m} or just have instructions in INSTALL to do so 2. Recommend users install groff

I am in the process of submitting a package to CRAN. R CMD check ran successfully on the package on my local computer, using R version 2.1.1. However, on the computers for CRAN (with version 2.10.0), the following errors occurred: Warning in parse_Rd("./man/predict.Rd", encoding = "unknown") : ./man/predict.Rd:28: unknown macro '\dquote' *** error on file

Hello. I have a server that sends a preformatted email when an event occur. What I need is that when Asterisk receives this email automatically dial a pre-recorded message. It doesn't have to dial ride away, maybe a scheduled cron job will be enough. Is that possible? Any hint? What should I be looking for? Thanks, and sorry for my lousy English -- Berm?dez Rafael -------------- next

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, I'm trying to enable the hexagon LLVM assembly parser. It seem like there is a lot of work that has been done to make this parsing straightforward. But.. Hexagon assembly does not follow the "Mnemonic Rx Rx ." format that is expected by the assembly parsing infrastructure, represented by: StringRef Mnemonic = ((ARMOperand*)Operands[0])->getToken(); This

I am writing a rd doc, and need to use "#" in a url adress. This would make: \url{http://www.xxxx.org/myfolder/#myanchor} Of course, I suppose this will not work because # is a special character starting a comment line in the rd dialect. I did not found a similar example in "Writing R exentions". I am not sure bout using \dQuote{a quotation}), and use \sQuote and \dQuote

Dear all When comparing sQuote("text") and dQuote("text") on MacOS X and Linux FC4 I get an inconsistent behavior (using the new release version R-2.6.0): sQuote: On Mac I get the correct result "'text'", but on FC4 the incorrect result "`text?". dQuote: On Mac I get the correct result "\"text\"", but on FC4 the incorrect

Dear all, I am getting an R CMD check warning about the PDF manual. I am having a hard time finding out what is wrong, here is the log of the Rd2pdf call. The full check (and other) log is at https://api.travis-ci.org/jobs/46373922/log.txt?deansi=true if anybody is interested, and the package itself is here: https://github.com/metacran/r-builder/tree/bintex/rbuildertest Thanks, Best, Gabor

Hi, I've got a buffalo 1TB DriveStation run in RAID 1 mode, i.e. 500G space available, but that beast is preformatted in vfat. Buffalo doesn't recommend to run it as ext2/ext3, so I mount a vfat drive wich has the limitations "no symlinks, no uids, no gids, etc.". As I just want to use the DriveStation as a backup target, I did the following: I created files of 4G size with