similar to: preformatted and '#' in manual pages

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

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

Dear all, On the Broadcom wiki page, I've moved the formatted codes from tables into preformatted blocks. This makes the raw wiki code easier to read, and is consistent with other wiki pages that I've come across during translation. Should the maintainers of that page find such a change undesirable, please feel free to revert. Regards, Timothy Lee

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

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{

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

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.

Hello, I 've messages in my log...it's regular...but I don?t know if this is a serious problem ! My conf : Samba 3.0.24 and Debian Etch Security Events =-=-=-=-=-=-=-= Aug 20 17:17:08 dios smbd[9051]: read_data: read failure for 4 bytes to client 10.x.x.x. Error = Aucun chemin d'acc?s pour atteindre l'h?te cible System Events =-=-=-=-=-=-= Aug 20 17:17:08 dios smbd[9051]:

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,

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

===8<==============Original message text=============== 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

>>>>> G?bor Cs?rdi <csardi.gabor at gmail.com> >>>>> on Thu, 8 Jan 2015 17:18:27 -0500 writes: > 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 >

On a CentOS 7 machine, I am at a loss with respect to an inability to run a full R CMD check as anything involving tex files ends in tears. We followed the README at CRAN and installed a large number of tex-live packages on this machine. But when a manual is created, we end up with what follows below. Here, I chopped some of the error messages, the key seems to be 'Insufficient extension

Hi, The following command: R CMD Rd2pdf --no-preview --output=./tmp.pdf --title=test genefu-package.Rd run against this file: https://hedgehog.fhcrc.org/bioconductor/trunk/madman/Rpacks/genefu/man/genefu-package.Rd (username: readonly; password: readonly) produces a very verbose error (see below) with R version 2.15.0 alpha (2012-03-07 r58622). The .Rd file has these lines in it: Version: \tab

On 29 May 2018 at 16:37, R P Herrold wrote: | On Tue, 29 May 2018, Dirk Eddelbuettel wrote: | | > On a CentOS 7 machine, I am at a loss with respect to an inability to run a | > full R CMD check as anything involving tex files ends in tears. | | Hi, Dirk | | Have fun at the upcoming conference at UIC | | I seem to have 56 font packages installed under CentOS 7 | locally, but then I work

Hi there everybody! I am completely new to linux and it's the first time I'm running linux (Ubuntu). Today I installed Wine and tried running Broken Sword 3 (note that I have nto configured Wine or anything: only installed and used the wine command). All I can see is a black screen (semms like the application tries to run) and the I return to desktop with an 800x600 resolution. What should

On 05/29/2018 04:53 PM, Dirk Eddelbuettel wrote: > I noticed it with a local, not-public package -- but it appears to apply with > any source package. I replicated with pkgKitten straight off CRAN and after > checking that it has a six page manual there. I'm having trouble reproducing this one. In my fresh CentOS 7 VM, I can pull the pkgKitten source down, and run R CMD Rd2pdf

Tom, On 30 May 2018 at 11:34, Tom Callaway wrote: | On 05/29/2018 04:53 PM, Dirk Eddelbuettel wrote: | > I noticed it with a local, not-public package -- but it appears to apply with | > any source package. I replicated with pkgKitten straight off CRAN and after | > checking that it has a six page manual there. | | I'm having trouble reproducing this one. In my fresh CentOS 7 VM, I

I was able to get the source code for ocfs2 and compile it. This worked and created the necessary .ko files Now I have to figure out why gnu parted 1.6.15 has bugs. when I try a partprobe on a partitioned firewire maxtor drive mount -t ocfs2 /dev/sdb1 /u01/oradata/orcl It says no such device.... Any ideas anyone?... Regards, Mandar Vengurlekar ----- Original Message ----- From: Mandar P