similar to: Passing tex parameter via texi2dvi

Dear all, I was hoping someone may know a way of running texi2dvi while ignoring bibtex errors, or any other work around (such as not running bibtex at all, if possible). The context is that I have an R program that does some calculations and writes a table into various folders, one per country for several countries. I have a latex file that takes the table as an input, and this latex file is

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

Hello, I am working on a big R project using Eclipse/StatET/Texlipse. I'd like to write a Latex document within that project but DO NOT want to Sweave it. It's pure Latex. Via the external tools configurations I set up 2 different versions to ensure that my latex document is processed correctly. Version 1 (System Call): library(tools) setwd("${container_loc}") file =

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 =

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

Hi, On both Unix and Windows there is a mechanism to add variables to the environment when R is started. I noticed that, on Unix, this mechanism is not used when R is started normally at the command line but only when it's started using the 'R CMD' syntax. One problem with this is some lack of consistent cross-platform behaviour. For example: On Linux: $ echo $TEXINPUTS $

We have received an email in Ubuntu alerting us that something strange was going on during the r-base 2.7.1 rc build (see [1]). It seems that there is an error during the convertion of R-FAQ.texi to pdf. The following excerpt, taken from [2], shows the problem: /bin/sh: line 0: test: too many arguments TEXINPUTS=".:$TEXINPUTS" /usr/bin/texi2dvi --texinfo="@set UseExternalXrefs

First I tried 'setenv R_SHELL /usr/local/bin/bash', as bash is the weapon of choice for the faculty wishing to use R, then ran ./configure as before. The ./configure output line using as R_SHELL for scripts ... /usr/local/bin/bash would seem to indicate that the R_SHELL environment variable was recognized and acknowledged. However, I got the same build error: gnumake[2]: Entering

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

Dear R-users, It is my understanding that cat(shQuote(a.string)) should print the origintal a.string. Is this right? I am not sure cat() correctly prints strings which are generated by triple-shQuote(): > shQuote(shQuote("a")) [1] "\"\\\"a\\\"\"" > cat(shQuote(shQuote(shQuote("a"))), '\n')

Dear R-users, It is my understanding that cat(shQuote(a.string)) should print the origintal a.string. Is this right? I am not sure cat() correctly prints strings which are generated by triple-shQuote(): > shQuote(shQuote("a")) [1] "\"\\\"a\\\"\"" > cat(shQuote(shQuote(shQuote("a"))), '\n')

Hi All, I am running Ubuntu Feisty (7.04) on a Thinkpad T41. I've installed the nowebm package for Ubuntu. Working from this HowTo: http://www.ci.tuwien.ac.at/~leisch/Sweave/example-1.Snw I try to compile the example *.Snw as in the Sweave manual: mdj at lapmdj:~/Desktop/Sweave/example1$ noweb example-1.Snw Can't open output file Despite the error, a *.tex file is produced. Now I am

> 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): >

I am getting this error on CentOS 8 CC dahdi-linux-complete-3.1.0+3.1.0/linux/drivers/dahdi/xpp/xpp.mod.o LD [M] dahdi-linux-complete-3.1.0+3.1.0/linux/drivers/dahdi/xpp/xpp.ko CC dahdi-linux-complete-3.1.0+3.1.0/linux/drivers/dahdi/xpp/xpp_usb.mod.o LD [M] dahdi-linux-complete-3.1.0+3.1.0/linux/drivers/dahdi/xpp/xpp_usb.ko make[2]: Leaving directory

Hi, I run into a problem with "R CMD Rd2dvi" command: it gives me "File `Rd.sty' not found" error (See the output message on the bottom). I get the same error when running "RCMD check". My system is: Windows 2000, R version 2.0.1, MiKTeX version 2.4. I do have a Rd.sty file in R_HOME/share/texm directory. I looked through newsgroups for any related discussions

I just installed R-1.7.0 on Darwin 6.6 (a.k.a. MacOS 10.2.6). 'make' and 'make check' run without any problems. 'make info' builds with no complaints, but 'make dvi' and 'make pdf' fail. I get refman.dvi and refman.pdf OK (with some warnings from pdftex that some names are referenced that do not exist), but R-FAQ.{dvi,pdf} fails as shown below. Attempts

Dear R-List, I'm trying to read an UTF-8-encoded text file which works fine under ##################################################################### ### CONFIG 1 > sessionInfo() R version 2.12.1 (2010-12-16) Platform: i386-pc-mingw32/i386 (32-bit) locale: [1] LC_COLLATE=German_Germany.1252 LC_CTYPE=German_Germany.1252 [3] LC_MONETARY=German_Germany.1252 LC_NUMERIC=C

Dear all, I need to test for the existence of an index on a table. This cannot be done with sqlPrimaryKeys as it is not a primary key. Therefore I select directly from the systemtable of SQL-Server 2000 named sysindexes. This works well with RODBC Version 1.2-5 but not with version 1.3-0. Here is the code of the test example: sink(file = "proto.txt", append = FALSE, type =

Dear list, I have a balance connected to the serial port of a windows machine ("COM1") and I read the text output of the balance with scan("COM1", what="character", sep="\n", n=1) after calling the previous line I press the print key on the balance which triggers sending one line of text to the serial connection and with R 2.9.2 I get something like Read

Dear developers, I have come across a (somewhat strange) change in the encoding of Sweave output from R-2.9.2pat to R-2.10.0beta (apparently specific to Rgui) on Windows installations. Of course, the NEWS file contains quite a few changes concerning encoding, but I was not able to locate an entry which explains the observed behaviour. I am not very familiar with encodings/locales/codepages,