similar to: Rd2pdf ignores tabs but not trailing spaces

Hi list, When using R CMD Rd2pdf, it is possible to set environment variable RD2PDF_INPUTENC to value "inputenx" and enjoy better support for UTF-8 characters (see ?Rd2pdf). This enables LaTeX package "inputenx" instead of "inputenc". Even better support for UTF-8 encoded characters can be had by better using the facilities provided by inputenx and making R CMD

> The command Rd2pdf was rather useful for opening a package's manual > when you don't have access to the Internet (by using latex to pdf > conversion). However the way the function seems to operate changed at > version 2.14 of R. The noted changes listed on CRAN for this function > are as follows (which doesn't seem like it would affect my usage as > below): >

On 26/09/2017 10:27 PM, Kasper Daniel Hansen wrote: > When I include the macros \packageAuthor, \packageDescription, > \packageTitle, \packageMaintainer in a XX-package.Rd file, R CMD Rd2pdf > fails with > > $ R CMD Rd2pdf mpra > Hmm ... looks like a package > Converting Rd files to LaTeX Error : mpra/man/mpra-package.Rd:6: file > './DESCRIPTION' does not exist

No, I do not get the same as you. I have tested with R-devel and R-patched compiled today. When I do R CMD Rd2pdf mpra I get (as reported a few days ago) Hmm ... looks like a package Converting Rd files to LaTeX Error : mpra/man/mpra-package.Rd:6: file './DESCRIPTION' does not exist whereas you (Kurt) reports that this works on zTree. When I do R CMD Rd2pdf mpra/man I get - a

Sorry for the noise. I assumed I could run this in the same directory as R CMD check. If I cd into the package dir, and run it like R CMD Rd2pdf man it works. I was a bit sleep deprived yesterday. The fact that the output starts by Hmm ... looks like a package threw me off. That output suggests it should work, I think. So I would suggests either 1) handling both package and man directories

Hi everyone, >From the currently available version of the package VBmix, I would like to retrieve the intermediate .tex file that generates the VBmix-manual.pdf file. Formerly, running R CMD check with --no-clean allowed to get this tex source from a hidden directory : this feature was removed, but can apparently still be accessed through R CMD Rd2pdf --no-clean. Surprisingly, while the

Hi all, Sorry if I seem a bit pissed because I am! Basically, I have written some script and I wanted to make a "documentation" for it using .Rd format. ############################################################################ I followed the example here in http://stat.ethz.ch/R-manual/R-devel/library/utils/html/prompt.html created the file plot.default.rd in my directory. But

On the local machine the command R11 CMD Rd2pdf survfit.Rd works fine. R12 CMD Rd2pdf survfit.Rd fails with the message below. Converting Rd files to LaTeX ... survfit.Rd Creating pdf output from LaTeX ... Error in texi2dvi("Rd2.tex", pdf = (out_ext == "pdf"), quiet = FALSE, : Running 'texi2dvi' on 'Rd2.tex' failed. Messages: sh: texi2dvi: command not

Hi, I am writing tool to simplify automated refactorings. One of prerequisites is have clean codebase, so a refactorer can be simple and created formatting inconsistencies can be eliminated by formatter. My plan to keep codebase clean is first run a cleanup systemwide, then keep it by hook/ periodicaly rerunning cleanup. I put it for now here. https://github.com/neleai/stylepp I ran a scripts

When I include the macros \packageAuthor, \packageDescription, \packageTitle, \packageMaintainer in a XX-package.Rd file, R CMD Rd2pdf fails with $ R CMD Rd2pdf mpra Hmm ... looks like a package Converting Rd files to LaTeX Error : mpra/man/mpra-package.Rd:6: file './DESCRIPTION' does not exist This does not happen if I comment out 4 occurrences of these 4 macros in mpra-package.Rd.

When I run R CMD Rd2pdf on the man pages of a package, ie R CMD Rd2pdf man I get Converting Rd files to LaTeX Warning in parse_Rd("man/mpra-package.Rd", encoding = "unknown", fragment = FALSE, : man/mpra-package.Rd:6: unknown macro '\packageTitle' Warning in parse_Rd("man/mpra-package.Rd", encoding = "unknown", fragment = FALSE, :

Hi, I want to create a pdf of my Man-pages from my package. Therefore I run in the terminal Rd2pdf on the package and a pdf of all the pages is created. After the titlepage there is the general package page, which includes "Description" and "Details" etc. Unfortunately after the Subtitle "Details" there is a pagebreak (and 3/4 white page) which I did not set

Hello everybody I'm am trying to build a pdf out of the Rd files that i wrote for a package, so that I can attach it to my thesis. if i Run Rd2pdf (or Rd2dvi) I get this error massage: Hmm ... looks like a package Converting Rd files to LaTeX . Creating pdf output from LaTeX ... Error in texi2dvi("Rd2.tex", pdf = (out_ext == "pdf"), quiet = FALSE, : Running

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

It seems that Markdown 1.0.1 strips off trailing spaces at the end of code blocks. Is this really what it's supposed to do? There might be reasons to include trailing spaces in code displayed on a web page -- for example, in demonstrating how to do a hard line break in markdown. Even if the trailing spaces aren't visible, they can be cut and pasted. Besides, Markdown 1.0.1 preserves

On Apr 25, 2013, at 9:42 AM, Christian Wiese wrote: > I created a pull request #27 which is fixing the issue. > > # nut-scanner -qNU > [nutdev1] > driver = "usbhid-ups" > port = "auto" > vendorid = "051D" > productid = "0002" > product = "Back-UPS ES 700G FW:871.O2 .I USB FW:O2" > serial = "5B1243T01934"

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

On Tue, Oct 13, 2015 at 5:17 PM, Geert Stappers via Syslinux <syslinux at zytor.com> wrote: > On Sat, Oct 10, 2015 at 03:10:26PM +0300, Ady via Syslinux wrote: >> From: Geert Stappers <stappers at nero.gpm.stappers.nl> >> > >> > com32/mboot/map.c: removed trailing spaces >> > >> > They were introduced by the patch for ELF64 support. >>

2015-10-14 1:45 UTC+02:00, Gene Cumm via Syslinux <syslinux at zytor.com>: > On Tue, Oct 13, 2015 at 5:17 PM, Geert Stappers via Syslinux > <syslinux at zytor.com> wrote: >> On Sat, Oct 10, 2015 at 03:10:26PM +0300, Ady via Syslinux wrote: >>> From: Geert Stappers <stappers at nero.gpm.stappers.nl> >>> > >>> > com32/mboot/map.c:

I have a character string and I would like to remove the leading and tailing white spaces. The example for 'sub' shows how to remove the trailing white spaces, but I still can't figure out how to remove both trailing and leading white spaces because I can't find any documentation for what "+$" means or what "\\s+$" means. Maybe its because I don't have a