similar to: Awkward escaping with five backslashes within \code{ } in new parse_Rd

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

Hello, I am not sure whether this is a bug or lack of R experience. However, I am using your Sweavelistingutil package, which is very nice. Obviously I use it to create LaTeX files. These are encoded in utf8. However, when I use the Sweavelistingutil is uses some funky character for "`" and "'" that is not recognized. Here is an example from my tex-file: ,---- |

Hello, recently I read about the SweaveListingUtils package and now I want to try it out. However, I can not make it work... Below a minimal example. The problem seems to be the following line (generated by SweaveListingPreparations()?): \ifthenelse{\boolean{Sweave@gin}}{\setkeys{Gin}{width=0.6\textwidth}}{}% If I comment out this line, it works. What can I do about this? I am using the

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

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{

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

Dear Colleagues: In producing a book or a handout I sometimes cut out a large part of the printed output of an R function, substituting ... for that chunk. Deleting non-essential output saves paper. It would be nice to have a capability in Sweave to allow the user to specify a starting and an ending regular expression that would identify consecutive lines of output to replace with ...,

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

Dear Group, I have made significant improvements to our Sweave template, have made the template self-contained (i.e., you can run it yourself and it will find the datasets it needs), and have included the output pdf file. This is at http://biostat.mc.vanderbilt.edu/SweaveTemplate . You will see in the pdf file the enhancements in how R code is pretty-printed, and I have added an example

Hola a todos: Con la entrada de R 3.0 en Debian Sid me acabo de llevar la sorpresa de que pgfSweave ya no esta mantenido [0]. He intentado compilarlo pero depende de otros paquetes que también se encuentran en el archivo: highlight y parser. En concreto este último falla al compilar (y ahí se acaba el intento). Estaba utilizando pgfSweave por la facilidad para incluir gráficos en Tikz -sin

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

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:

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

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)%>'}" >

Dear expeRts, What's a 'good' (nice-looking, easy-to-read) setup for the LaTeX package 'listings' to display R code? The two versions below are partly inspired by the settings of the package SweaveListingUtils and http://r.789695.n4.nabble.com/R-How-to-format-R-code-in-LaTex-documents-td816055.html Any suggestions, comments, or improvements are welcome. Cheers, Marius ###

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