search for: pkg2tex

...CMD Rd2pdf <package>.Rcheck/<package> ...and the source of the difference is the presence (or absence) of the <package>.Rcheck/<package>/latex directory. If I temporarily move it away during an R CMD check --install-args=--latex run, the command succeeds. Indeed, tools:::.pkg2tex says >> ## First check for a latex dir (from R CMD INSTALL --latex). >> ## Second guess is this is a >= 2.10.0 package with stored .rds >> ## files. >> ## If it does not exist, guess this is a source package. >> latexdir <- file.path(pkgdir, "latex")...

...t;.Rcheck/<package> > ...and the source of the difference is the presence (or absence) of the > <package>.Rcheck/<package>/latex directory. If I temporarily move it > away during an R CMD check --install-args=--latex run, the command > succeeds. > Indeed, tools:::.pkg2tex says >>> ## First check for a latex dir (from R CMD INSTALL --latex). >>> ## Second guess is this is a >= 2.10.0 package with stored .rds >>> ## files. >>> ## If it does not exist, guess this is a source package. >>> latexdir <- file.path(pkgdir,...

...age> >> ...and the source of the difference is the presence (or absence) of the >> <package>.Rcheck/<package>/latex directory. If I temporarily move it >> away during an R CMD check --install-args=--latex run, the command >> succeeds. >> Indeed, tools:::.pkg2tex says >>>> ## First check for a latex dir (from R CMD INSTALL --latex). >>>> ## Second guess is this is a >= 2.10.0 package with stored .rds >>>> ## files. >>>> ## If it does not exist, guess this is a source package. >>>> latexdir <-...

Hi R-devels, would it be possible to enhance either promptPackage() or the default indexing mechanism for packages so that -- if it exists -- (the contents of) file <pkgname>-package.Rd is sorted first in * the .dvi / .pdf documentation file * the .chm documentation file * the package 00index.html documentation file ? So far I found the following "hand-made" solution

Hello, is the reference manual also available with each explained function beginning on a seperate page? Or can this somehow be done easily? I prefer reading documentation on paper, but printing makes more sense, when each function can be printed seperated (like in man-pages). Any idea, how to achieve this? TIA, Oliver

Hi, this is to report some minor UTF-8 encoding issue with R CMD check with option --install-args="--latex" (and possibly more install-args). More specifically, in my Windows system (see the cloud link below for details on my system), but also on the Linux machine of my collaborator Matthias Kohl (CC), the following command throws errors: ????? R CMD check

When I create a manual for a package that I create and use locally, e.g. via R CMD Rd2dvi --pdf foo where ``foo'' is the name of the directory containing the source for the package (also named ``foo'') the resulting manual does not appear to have an index. The package.pdf files appearing on CRAN all seem to have indices. What must I do to get an index appended to the

...s-2.7-bioc/meat/IRanges.Rcheck/00install.out' for details. Content of IRanges.Rcheck/00install.out: * install options '--no-html --no-multiarch' Warning: unknown option '-l' Warning: unknown option '--no-html' Warning: unknown option '--no-multiarch' Error in .pkg2tex(files, outfile, encoding = encoding, append = append, : this package does not have either a 'latex' or a (source) 'man' directory >>> On 32-bit Windows: R\bin\R.exe CMD check --no-vignettes --timings keggorthology_2.1.1.tar.gz * using log directory 'E:/biocbld/b...

...act-usage creating src/unix/Makefile creating src/unix/X11/Makefile creating src/unix/gnome/Makefile creating tests/Makefile creating tests/Examples/Makefile creating tools/Makefile creating tools/Rdnewer creating tools/help2man creating tools/keyword-test creating tools/install-info creating tools/pkg2tex creating src/include/config.h R is now configured for sparc-sun-solaris2.6 Source directory: . Installation directory: /usr/local C compiler: gcc -g -O2 C++ compiler: c++ -g -O2 FORTRAN compiler: g77 -g -O2 X11 support: yes...