similar to: running texi2dvi without running bibtex

Dear All I am trying to specify the output directory and the directory for the log files (the same) for texi2dvi. The default for my windows computer is C:\Users\...\Documents which I do not want. The help guide: texinputs NULL or a character vector of paths to add to the LaTeX and bibtex input search paths. is a little cryptic for me this morning I have tried texi2dvi(file =

Hello: Changes in R seem to have broken the sos vignette, and I don't know how to fix it. The build on R-forge, "https://r-forge.r-project.org/R/?group_id=235&log=build_src&pkg=sos&flavor=patched", ends as follows: Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : Running 'texi2dvi' on 'sos.tex' failed. LaTeX

Hello, I'm running R2.10, Eclipse, StatEt and MikTex 2.8 to create Sweave documents, and everything seems to work great, until today... I was trying to add citations from a Bibtex file, but I just got [?] citations. However, if I open the .tex file that StatEt created in MikTex and run the latex+bibtex+pdflatex command, the citations are present. Does anyone know how to either configure

Hello, I have the following makefile. The problem is that the bibliography doesn t work. Any help would be appreciated! I really don t don t what to do..:-( # The sources of the report (tex, Rnw and other files (e.g. bib, idx)) TEX_CMPS = Report problem RNW_CMPS = prop1 prop2 ExeExps OTHER = Report.bib # The name of the report to produce all: Report.pdf code: $(RNW_CMPS:=.R) clean: rm

Hello: I could use help understanding an error reported by "R CMD build sos" that's new with R 3.3.0: Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : Running 'texi2dvi' on 'sos.tex' failed. LaTeX errors: ! Undefined control sequence. l.1 \Sconcordance {concordance:sos.tex:sos.Rnw:% The control sequence at

Dear list, I am trying to produce a pdf manual using Rtools (version 3.1.0.1936) on Windows 8 (64-bit). I am also aware of the inconsolata issue posted in the forum (https://stat.ethz.ch/pipermail/r-devel/2013-June/066850.html), and then I have installed the patched version of R-3.0.1. However I still have some errors with the following message: R CMD Rd2pdf mypack Hmm ... looks like a package

On 17/06/2016 10:21 PM, Spencer Graves wrote: > Hello: > > > Changes in R seem to have broken the sos vignette, and I don't > know how to fix it. The build on R-forge, > "https://r-forge.r-project.org/R/?group_id=235&log=build_src&pkg=sos&flavor=patched", > ends as follows: > > > Error in texi2dvi(file = file, pdf = TRUE, clean =

R Community, I often am in need of viewing the reference manuals of packages and do not have Internet access. I have used the code: path <- find.package('tm') system(paste(shQuote(file.path(R.home("bin"), "R")),"CMD", "Rd2pdf",shQuote(path))) someone kindly provided from this help list to generate the manuals from the latex files. This

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

I am trying to pass a additional argument to texi2dvi, for example to use the aux-directory. Looks like this is not possible via options: options(texi2dvi='texi2dvi --tex-option="-aux-directory=auxdir"') texi2dvi(file = "GBPL3.tex", pdf = TRUE) #Error in system(paste(shQuote(texi2dvi), "--version"), intern = TRUE) : # '"texi2dvi

Dear expeRts, below are two examples of using texi2dvi. The problem becomes clear from the second example: on cleaning, texi2dvi also deletes the generated .pdf file. Is there a solution? Cheers, Marius ## Example 1: texi2dvi cleans fine, without deleting the generated .pdf require(tools) sink(file="myLaTeXFile1.tex") cat("\\documentclass{article}\n")

L.S. I noticed weird tools::texi2dvi behaviour on R-alpha when specifying an absolute path to the .tex file. The same phenomenon also appears to occur on R-2.12.2, so maybe the issue is independent of R. I hope I did not overlook any important information. Best, Tobias > require(tools) Loading required package: tools > getwd() [1] "/home/tobias" >

Dear R-devel, Question: How can I get Sweave to recognize that the \thebibliography section is already created and generate the vignette pdf with a single pass? Or is there a way to let R CMD build know that Sweave needs to be run twice? If (1) is not possible, any suggestions how to auto-generate a crude generic bibtex .bib file from my existing document? Background: I maintain

R CMD build fails with recent R-devel because it is looking for texi2dvi in /usr/local/bin, but on this system, MacTex has installed it in /usr/bin. $ R CMD build IRanges * checking for file 'IRanges/DESCRIPTION' ... OK * preparing 'IRanges': * checking DESCRIPTION meta-information ... OK * cleaning src * installing the package to build vignettes * creating vignettes ... ERROR

I have two versions of a bibtex database which have gotten badly out of sync. I need to find find all the entries in bib2 which are not contained in bib1, according to their bibtex keys. But I can't figure out how to extract a list of the bibentry keys in these databases. A minor question: Is there someway to prevent read.bib from ignoring entries that do not contain all required fields?

Back in 2010 I raised this issue, and there was some discussion, https://stat.ethz.ch/pipermail/r-devel/2010-November/058987.html The goal, then, as now is to have a way to produce a bibtex-clean .bib file (i.e., not requiring manual editing except in unusual circumstances) reflecting installed packages for use in writing where one often needs/wants to cite all packages used in a given

I noticed a shQuote fix for Windows in the svn logs. Just wanted to point out that this will favorably affect texi2dvi on Windows which previously used UNIX quoting and so generated an incorrect Windows command. (Note that texi2dvi is used when creating vignettes.) Another problem is that the recommended tex distribution for Windows, fptex, does not have texi2dvi in the first place. The

----- Original Message ----- > From: "Simon Urbanek" <simon.urbanek at r-project.org> > To: "Dan Tenenbaum" <dtenenba at fredhutch.org> > Cc: "R-devel" <r-devel at r-project.org> > Sent: Monday, January 12, 2015 5:50:35 PM > Subject: Re: [Rd] R CMD build looking for texi2dvi in the wrong place (R-devel) > > Dan, > > On

Hi is there an easy and fast way, to generate a BibTeX file of all installed / loaded packages and R? I know about toBibtex(citation()) to extract the BibTeX for a single package, but how can I generate a file containg citations for all installed / loaded packages? Cheers, Rainer -- NEW GERMAN FAX NUMBER!!! Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT),

Dear lists: I am somewhat puzzled by the use of texi2dvi/pdflatex in R2.7.0. When building EBImage (bioconductor) with 2.7.0 I get the same error both in Windows and Linux, which reads the following: ** building package indices ... * DONE (EBImage) * creating vignettes ... ERROR /usr/bin/texi2dvi: pdflatex exited with bad status, quitting. Error in texi2dvi(file = bft, pdf = TRUE, clean =